Instruction and Logic for Interrupt and Exception Handling

ABSTRACT

A processor includes a processor trace logical unit to produce branch execution records from execution of instructions. The processor further includes logic to determine that a condition has occurred on the processor during execution of the instructions. The condition is to include an asynchronous event or a return from a software handler for an asynchronous event. The processor further includes logic to determine whether event tracing is enabled for the processor. The processor also includes logic to generate a control flow event (CFE) packet. The CFE packet is to indicate a type of the condition. The processor further includes logic to generate an indicator of an instruction address that generated the condition.

FIELD OF THE INVENTION

The present disclosure pertains to the field of processing logic, microprocessors, and associated instruction set architecture that, when executed by the processor or other processing logic, perform logical, mathematical, or other functional operations.

DESCRIPTION OF RELATED ART

Multiprocessor systems are becoming more and more common. Applications of multiprocessor systems include dynamic domain partitioning all the way down to desktop computing. In order to take advantage of multiprocessor systems, code to be executed may be separated into multiple threads for execution by various processing entities. Each thread may be executed in parallel with one another. Furthermore, in order to increase the utility of a processing entity, out-of-order execution may be employed. Out-of-order execution may execute instructions as input to such instructions is made available. Thus, an instruction that appears later in a code sequence may be executed before an instruction appearing earlier in a code sequence. Interrupts may be generated from such instructions. The interrupts may be masked so that other instructions may operate without interruption.

DESCRIPTION OF THE FIGURES

Embodiments are illustrated by way of example and not limitation in the Figures of the accompanying drawings:

FIG. 1A is a block diagram of an exemplary computer system formed with a processor that may include execution units to execute an instruction, in accordance with embodiments of the present disclosure;

FIG. 1B illustrates a data processing system, in accordance with embodiments of the present disclosure;

FIG. 1C illustrates other embodiments of a data processing system for performing text string comparison operations;

FIG. 2 is a block diagram of the micro-architecture for a processor that may include logic circuits to perform instructions, in accordance with embodiments of the present disclosure;

FIG. 3A illustrates various packed data type representations in multimedia registers, in accordance with embodiments of the present disclosure;

FIG. 3B illustrates possible in-register data storage formats, in accordance with embodiments of the present disclosure;

FIG. 3C illustrates various signed and unsigned packed data type representations in multimedia registers, in accordance with embodiments of the present disclosure;

FIG. 3D illustrates an embodiment of an operation encoding format;

FIG. 3E illustrates another possible operation encoding format having forty or more bits, in accordance with embodiments of the present disclosure;

FIG. 3F illustrates yet another possible operation encoding format, in accordance with embodiments of the present disclosure;

FIG. 4A is a block diagram illustrating an in-order pipeline and a register renaming stage, out-of-order issue/execution pipeline, in accordance with embodiments of the present disclosure;

FIG. 4B is a block diagram illustrating an in-order architecture core and a register renaming logic, out-of-order issue/execution logic to be included in a processor, in accordance with embodiments of the present disclosure;

FIG. 5A is a block diagram of a processor, in accordance with embodiments of the present disclosure;

FIG. 5B is a block diagram of an example implementation of a core, in accordance with embodiments of the present disclosure;

FIG. 6 is a block diagram of a system, in accordance with embodiments of the present disclosure;

FIG. 7 is a block diagram of a second system, in accordance with embodiments of the present disclosure;

FIG. 8 is a block diagram of a third system in accordance with embodiments of the present disclosure;

FIG. 9 is a block diagram of a system-on-a-chip, in accordance with embodiments of the present disclosure;

FIG. 10 illustrates a processor containing a central processing unit and a graphics processing unit which may perform at least one instruction, in accordance with embodiments of the present disclosure;

FIG. 11 is a block diagram illustrating the development of IP cores, in accordance with embodiments of the present disclosure;

FIG. 12 illustrates how an instruction of a first type may be emulated by a processor of a different type, in accordance with embodiments of the present disclosure;

FIG. 13 illustrates a block diagram contrasting the use of a software instruction converter to convert binary instructions in a source instruction set to binary instructions in a target instruction set, in accordance with embodiments of the present disclosure;

FIG. 14 is a block diagram of an instruction set architecture of a processor, in accordance with embodiments of the present disclosure;

FIG. 15 is a more detailed block diagram of an instruction set architecture of a processor, in accordance with embodiments of the present disclosure;

FIG. 16 is a block diagram of an execution pipeline for an instruction set architecture of a processor, in accordance with embodiments of the present disclosure;

FIG. 17 is a block diagram of an electronic device for utilizing a processor, in accordance with embodiments of the present disclosure;

FIG. 18 is a block diagram of a system for interrupt and exception handling, according to embodiments of the present disclosure;

FIG. 19 is more detailed block diagram of elements of a system for interrupt and exception handling, according to embodiments of the present disclosure;

FIG. 20 is an illustration of example operation of the system for interrupt and exception handling, in according to embodiments of the present disclosure;

FIG. 21 is an illustration of example operation of the system for tracking interrupt masking, according to embodiments of the present disclosure;

FIG. 22 is flow chart of a method for interrupt and exception handling according to embodiments of the present disclosure; and

FIG. 23 is flow chart of a method for tracking interrupt masking according to embodiments of the present disclosure.

DETAILED DESCRIPTION

The following description describes an instruction and processing logic for interrupt and exception handling within or in association with a processor, virtual processor, package, computer system, or other processing apparatus. In one embodiment, such an apparatus may include an out-of-order processor. In another embodiment, such an apparatus may include intellectual property (IP) cores. In yet another embodiment, such an apparatus may include a System-on-Chip (SoC).

In the following description, numerous specific details such as processing logic, processor types, micro-architectural conditions, events, enablement mechanisms, and the like are set forth in order to provide a more thorough understanding of embodiments of the present disclosure. It will be appreciated, however, by one skilled in the art that the embodiments may be practiced without such specific details. Additionally, some well-known structures, circuits, and the like have not been shown in detail to avoid unnecessarily obscuring embodiments of the present disclosure.

Although the following embodiments are described with reference to a processor, other embodiments are applicable to other types of integrated circuits and logic devices. Similar techniques and teachings of embodiments of the present disclosure may be applied to other types of circuits or semiconductor devices that may benefit from higher pipeline throughput and improved performance. The teachings of embodiments of the present disclosure are applicable to any processor or machine that performs data manipulations. However, the embodiments are not limited to processors or machines that perform 512-bit, 256-bit, 128-bit, 64-bit, 32-bit, or 16-bit data operations and may be applied to any processor and machine in which manipulation or management of data may be performed. In addition, the following description provides examples, and the accompanying drawings show various examples for the purposes of illustration. However, these examples should not be construed in a limiting sense as they are merely intended to provide examples of embodiments of the present disclosure rather than to provide an exhaustive list of all possible implementations of embodiments of the present disclosure.

Although the below examples describe instruction handling and distribution in the context of execution units and logic circuits, other embodiments of the present disclosure may be accomplished by way of a data or instructions stored on a machine-readable, tangible medium, which when performed by a machine cause the machine to perform functions consistent with at least one embodiment of the disclosure. In one embodiment, functions associated with embodiments of the present disclosure are embodied in machine-executable instructions. The instructions may be used to cause a general-purpose or special-purpose processor that may be programmed with the instructions to perform the steps of the present disclosure. Embodiments of the present disclosure may be provided as a computer program product or software which may include a machine or computer-readable medium having stored thereon instructions which may be used to program a computer (or other electronic devices) to perform one or more operations according to embodiments of the present disclosure. Furthermore, steps of embodiments of the present disclosure might be performed by specific hardware components that contain fixed-function logic for performing the steps, or by any combination of programmed computer components and fixed-function hardware components.

Instructions used to program logic to perform embodiments of the present disclosure may be stored within a memory in the system, such as DRAM, cache, flash memory, or other storage. Furthermore, the instructions may be distributed via a network or by way of other computer-readable media. Thus a machine-readable medium may include any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computer), but is not limited to, floppy diskettes, optical disks, Compact Discs, Read-Only Memory (CD-ROMs), and magneto-optical disks, Read-Only Memory (ROMs), Random Access Memory (RAM), Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), magnetic or optical cards, flash memory, or a tangible, machine-readable storage used in the transmission of information over the Internet via electrical, optical, acoustical or other forms of propagated signals (e.g., carrier waves, infrared signals, digital signals, etc.). Accordingly, the computer-readable medium may include any type of tangible machine-readable medium suitable for storing or transmitting electronic instructions or information in a form readable by a machine (e.g., a computer).

A design may go through various stages, from creation to simulation to fabrication. Data representing a design may represent the design in a number of manners. First, as may be useful in simulations, the hardware may be represented using a hardware description language or another functional description language. Additionally, a circuit level model with logic and/or transistor gates may be produced at some stages of the design process. Furthermore, designs, at some stage, may reach a level of data representing the physical placement of various devices in the hardware model. In cases wherein some semiconductor fabrication techniques are used, the data representing the hardware model may be the data specifying the presence or absence of various features on different mask layers for masks used to produce the integrated circuit. In any representation of the design, the data may be stored in any form of a machine-readable medium. A memory or a magnetic or optical storage such as a disc may be the machine-readable medium to store information transmitted via optical or electrical wave modulated or otherwise generated to transmit such information. When an electrical carrier wave indicating or carrying the code or design is transmitted, to the extent that copying, buffering, or retransmission of the electrical signal is performed, a new copy may be made. Thus, a communication provider or a network provider may store on a tangible, machine-readable medium, at least temporarily, an article, such as information encoded into a carrier wave, embodying techniques of embodiments of the present disclosure.

In modern processors, a number of different execution units may be used to process and execute a variety of code and instructions. Some instructions may be quicker to complete while others may take a number of clock cycles to complete. The faster the throughput of instructions, the better the overall performance of the processor. Thus it would be advantageous to have as many instructions execute as fast as possible. However, there may be certain instructions that have greater complexity and require more in terms of execution time and processor resources, such as floating point instructions, load/store operations, data moves, etc.

As more computer systems are used in internet, text, and multimedia applications, additional processor support has been introduced over time. In one embodiment, an instruction set may be associated with one or more computer architectures, including data types, instructions, register architecture, addressing modes, memory architecture, interrupt and exception handling, and external input and output (I/O).

In one embodiment, the instruction set architecture (ISA) may be implemented by one or more micro-architectures, which may include processor logic and circuits used to implement one or more instruction sets. Accordingly, processors with different micro-architectures may share at least a portion of a common instruction set. For example, Intel® Pentium 4 processors, Intel® Core™ processors, and processors from Advanced Micro Devices, Inc. of Sunnyvale Calif. implement nearly identical versions of the x86 instruction set (with some extensions that have been added with newer versions), but have different internal designs. Similarly, processors designed by other processor development companies, such as ARM Holdings, Ltd., MIPS, or their licensees or adopters, may share at least a portion a common instruction set, but may include different processor designs. For example, the same register architecture of the ISA may be implemented in different ways in different micro-architectures using new or well-known techniques, including dedicated physical registers, one or more dynamically allocated physical registers using a register renaming mechanism (e.g., the use of a Register Alias Table (RAT), a Reorder Buffer (ROB) and a retirement register file. In one embodiment, registers may include one or more registers, register architectures, register files, or other register sets that may or may not be addressable by a software programmer.

An instruction may include one or more instruction formats. In one embodiment, an instruction format may indicate various fields (number of bits, location of bits, etc.) to specify, among other things, the operation to be performed and the operands on which that operation will be performed. In a further embodiment, some instruction formats may be further defined by instruction templates (or sub-formats). For example, the instruction templates of a given instruction format may be defined to have different subsets of the instruction format's fields and/or defined to have a given field interpreted differently. In one embodiment, an instruction may be expressed using an instruction format (and, if defined, in a given one of the instruction templates of that instruction format) and specifies or indicates the operation and the operands upon which the operation will operate.

Scientific, financial, auto-vectorized general purpose, RMS (recognition, mining, and synthesis), and visual and multimedia applications (e.g., 2D/3D graphics, image processing, video compression/decompression, voice recognition algorithms and audio manipulation) may require the same operation to be performed on a large number of data items. In one embodiment, Single Instruction Multiple Data (SIMD) refers to a type of instruction that causes a processor to perform an operation on multiple data elements. SIMD technology may be used in processors that may logically divide the bits in a register into a number of fixed-sized or variable-sized data elements, each of which represents a separate value. For example, in one embodiment, the bits in a 64-bit register may be organized as a source operand containing four separate 16-bit data elements, each of which represents a separate 16-bit value. This type of data may be referred to as ‘packed’ data type or ‘vector’ data type, and operands of this data type may be referred to as packed data operands or vector operands. In one embodiment, a packed data item or vector may be a sequence of packed data elements stored within a single register, and a packed data operand or a vector operand may a source or destination operand of a SIMD instruction (or ‘packed data instruction’ or a ‘vector instruction’). In one embodiment, a SIMD instruction specifies a single vector operation to be performed on two source vector operands to generate a destination vector operand (also referred to as a result vector operand) of the same or different size, with the same or different number of data elements, and in the same or different data element order.

SIMD technology, such as that employed by the Intel® Core™ processors having an instruction set including x86, MMX™, Streaming SIMD Extensions (SSE), SSE2, SSE3, SSE4.1, and SSE4.2 instructions, ARM processors, such as the ARM Cortex® family of processors having an instruction set including the Vector Floating Point (VFP) and/or NEON instructions, and MIPS processors, such as the Loongson family of processors developed by the Institute of Computing Technology (ICT) of the Chinese Academy of Sciences, has enabled a significant improvement in application performance (Core™ and MMX™ are registered trademarks or trademarks of Intel Corporation of Santa Clara, Calif.).

In one embodiment, destination and source registers/data may be generic terms to represent the source and destination of the corresponding data or operation. In some embodiments, they may be implemented by registers, memory, or other storage areas having other names or functions than those depicted. For example, in one embodiment, “DEST1” may be a temporary storage register or other storage area, whereas “SRC1” and “SRC2” may be a first and second source storage register or other storage area, and so forth. In other embodiments, two or more of the SRC and DEST storage areas may correspond to different data storage elements within the same storage area (e.g., a SIMD register). In one embodiment, one of the source registers may also act as a destination register by, for example, writing back the result of an operation performed on the first and second source data to one of the two source registers serving as a destination registers.

FIG. 1A is a block diagram of an exemplary computer system formed with a processor that may include execution units to execute an instruction, in accordance with embodiments of the present disclosure. System 100 may include a component, such as a processor 102 to employ execution units including logic to perform algorithms for process data, in accordance with the present disclosure, such as in the embodiment described herein. System 100 may be representative of processing systems based on the PENTIUM® III, PENTIUM® 4, Xeon™, Itanium®, XScale™ and/or StrongARM™ microprocessors available from Intel Corporation of Santa Clara, Calif., although other systems (including PCs having other microprocessors, engineering workstations, set-top boxes and the like) may also be used. In one embodiment, sample system 100 may execute a version of the WINDOWS™ operating system available from Microsoft Corporation of Redmond, Wash., although other operating systems (UNIX and Linux for example), embedded software, and/or graphical user interfaces, may also be used. Thus, embodiments of the present disclosure are not limited to any specific combination of hardware circuitry and software.

Embodiments are not limited to computer systems. Embodiments of the present disclosure may be used in other devices such as handheld devices and embedded applications. Some examples of handheld devices include cellular phones, Internet Protocol devices, digital cameras, personal digital assistants (PDAs), and handheld PCs. Embedded applications may include a micro controller, a digital signal processor (DSP), system on a chip, network computers (NetPC), set-top boxes, network hubs, wide area network (WAN) switches, or any other system that may perform one or more instructions in accordance with at least one embodiment.

Computer system 100 may include a processor 102 that may include one or more execution units 108 to perform an algorithm to perform at least one instruction in accordance with one embodiment of the present disclosure. One embodiment may be described in the context of a single processor desktop or server system, but other embodiments may be included in a multiprocessor system. System 100 may be an example of a ‘hub’ system architecture. System 100 may include a processor 102 for processing data signals. Processor 102 may include a complex instruction set computer (CISC) microprocessor, a reduced instruction set computing (RISC) microprocessor, a very long instruction word (VLIW) microprocessor, a processor implementing a combination of instruction sets, or any other processor device, such as a digital signal processor, for example. In one embodiment, processor 102 may be coupled to a processor bus 110 that may transmit data signals between processor 102 and other components in system 100. The elements of system 100 may perform conventional functions that are well known to those familiar with the art.

In one embodiment, processor 102 may include a Level 1 (L1) internal cache memory 104. Depending on the architecture, the processor 102 may have a single internal cache or multiple levels of internal cache. In another embodiment, the cache memory may reside external to processor 102. Other embodiments may also include a combination of both internal and external caches depending on the particular implementation and needs. Register file 106 may store different types of data in various registers including integer registers, floating point registers, status registers, and instruction pointer register.

Execution unit 108, including logic to perform integer and floating point operations, also resides in processor 102. Processor 102 may also include a microcode (ucode) ROM that stores microcode for certain macroinstructions. In one embodiment, execution unit 108 may include logic to handle a packed instruction set 109. By including the packed instruction set 109 in the instruction set of a general-purpose processor 102, along with associated circuitry to execute the instructions, the operations used by many multimedia applications may be performed using packed data in a general-purpose processor 102. Thus, many multimedia applications may be accelerated and executed more efficiently by using the full width of a processor's data bus for performing operations on packed data. This may eliminate the need to transfer smaller units of data across the processor's data bus to perform one or more operations one data element at a time.

Embodiments of an execution unit 108 may also be used in micro controllers, embedded processors, graphics devices, DSPs, and other types of logic circuits. System 100 may include a memory 120. Memory 120 may be implemented as a Dynamic Random Access Memory (DRAM) device, a Static Random Access Memory (SRAM) device, flash memory device, or other memory device. Memory 120 may store instructions and/or data represented by data signals that may be executed by processor 102.

A system logic chip 116 may be coupled to processor bus 110 and memory 120. System logic chip 116 may include a memory controller hub (MCH). Processor 102 may communicate with MCH 116 via a processor bus 110. MCH 116 may provide a high bandwidth memory path 118 to memory 120 for instruction and data storage and for storage of graphics commands, data and textures. MCH 116 may direct data signals between processor 102, memory 120, and other components in system 100 and to bridge the data signals between processor bus 110, memory 120, and system I/O 122. In some embodiments, the system logic chip 116 may provide a graphics port for coupling to a graphics controller 112. MCH 116 may be coupled to memory 120 through a memory interface 118. Graphics card 112 may be coupled to MCH 116 through an Accelerated Graphics Port (AGP) interconnect 114.

System 100 may use a proprietary hub interface bus 122 to couple MCH 116 to I/O controller hub (ICH) 130. In one embodiment, ICH 130 may provide direct connections to some I/O devices via a local I/O bus. The local I/O bus may include a high-speed I/O bus for connecting peripherals to memory 120, chipset, and processor 102. Examples may include the audio controller, firmware hub (flash BIOS) 128, wireless transceiver 126, data storage 124, legacy I/O controller containing user input and keyboard interfaces, a serial expansion port such as Universal Serial Bus (USB), and a network controller 134. Data storage device 124 may comprise a hard disk drive, a floppy disk drive, a CD-ROM device, a flash memory device, or other mass storage device.

For another embodiment of a system, an instruction in accordance with one embodiment may be used with a system on a chip. One embodiment of a system on a chip comprises of a processor and a memory. The memory for one such system may include a flash memory. The flash memory may be located on the same die as the processor and other system components. Additionally, other logic blocks such as a memory controller or graphics controller may also be located on a system on a chip.

FIG. 1B illustrates a data processing system 140 which implements the principles of embodiments of the present disclosure. It will be readily appreciated by one of skill in the art that the embodiments described herein may operate with alternative processing systems without departure from the scope of embodiments of the disclosure.

Computer system 140 comprises a processing core 159 for performing at least one instruction in accordance with one embodiment. In one embodiment, processing core 159 represents a processing unit of any type of architecture, including but not limited to a CISC, a RISC or a VLIW-type architecture. Processing core 159 may also be suitable for manufacture in one or more process technologies and by being represented on a machine-readable media in sufficient detail, may be suitable to facilitate said manufacture.

Processing core 159 comprises an execution unit 142, a set of register files 145, and a decoder 144. Processing core 159 may also include additional circuitry (not shown) which may be unnecessary to the understanding of embodiments of the present disclosure. Execution unit 142 may execute instructions received by processing core 159. In addition to performing typical processor instructions, execution unit 142 may perform instructions in packed instruction set 143 for performing operations on packed data formats. Packed instruction set 143 may include instructions for performing embodiments of the disclosure and other packed instructions. Execution unit 142 may be coupled to register file 145 by an internal bus. Register file 145 may represent a storage area on processing core 159 for storing information, including data. As previously mentioned, it is understood that the storage area may store the packed data might not be critical. Execution unit 142 may be coupled to decoder 144. Decoder 144 may decode instructions received by processing core 159 into control signals and/or microcode entry points. In response to these control signals and/or microcode entry points, execution unit 142 performs the appropriate operations. In one embodiment, the decoder may interpret the opcode of the instruction, which will indicate what operation should be performed on the corresponding data indicated within the instruction.

Processing core 159 may be coupled with bus 141 for communicating with various other system devices, which may include but are not limited to, for example, Synchronous Dynamic Random Access Memory (SDRAM) control 146, Static Random Access Memory (SRAM) control 147, burst flash memory interface 148, Personal Computer Memory Card International Association (PCMCIA)/Compact Flash (CF) card control 149, Liquid Crystal Display (LCD) control 150, Direct Memory Access (DMA) controller 151, and alternative bus master interface 152. In one embodiment, data processing system 140 may also comprise an I/O bridge 154 for communicating with various I/O devices via an I/O bus 153. Such I/O devices may include but are not limited to, for example, Universal Asynchronous Receiver/Transmitter (UART) 155, Universal Serial Bus (USB) 156, Bluetooth wireless UART 157 and I/O expansion interface 158.

One embodiment of data processing system 140 provides for mobile, network and/or wireless communications and a processing core 159 that may perform SIMD operations including a text string comparison operation. Processing core 159 may be programmed with various audio, video, imaging and communications algorithms including discrete transformations such as a Walsh-Hadamard transform, a fast Fourier transform (FFT), a discrete cosine transform (DCT), and their respective inverse transforms; compression/decompression techniques such as color space transformation, video encode motion estimation or video decode motion compensation; and modulation/demodulation (MODEM) functions such as pulse coded modulation (PCM).

FIG. 1C illustrates other embodiments of a data processing system that performs SIMD text string comparison operations. In one embodiment, data processing system 160 may include a main processor 166, a SIMD coprocessor 161, a cache memory 167, and an input/output system 168. Input/output system 168 may optionally be coupled to a wireless interface 169. SIMD coprocessor 161 may perform operations including instructions in accordance with one embodiment. In one embodiment, processing core 170 may be suitable for manufacture in one or more process technologies and by being represented on a machine-readable media in sufficient detail, may be suitable to facilitate the manufacture of all or part of data processing system 160 including processing core 170.

In one embodiment, SIMD coprocessor 161 comprises an execution unit 162 and a set of register files 164. One embodiment of main processor 165 comprises a decoder 165 to recognize instructions of instruction set 163 including instructions in accordance with one embodiment for execution by execution unit 162. In other embodiments, SIMD coprocessor 161 also comprises at least part of decoder 165 to decode instructions of instruction set 163. Processing core 170 may also include additional circuitry (not shown) which may be unnecessary to the understanding of embodiments of the present disclosure.

In operation, main processor 166 executes a stream of data processing instructions that control data processing operations of a general type including interactions with cache memory 167, and input/output system 168. Embedded within the stream of data processing instructions may be SIMD coprocessor instructions. Decoder 165 of main processor 166 recognizes these SIMD coprocessor instructions as being of a type that should be executed by an attached SIMD coprocessor 161. Accordingly, main processor 166 issues these SIMD coprocessor instructions (or control signals representing SIMD coprocessor instructions) on the coprocessor bus 166. From coprocessor bus 166, these instructions may be received by any attached SIMD coprocessors. In this case, SIMD coprocessor 161 may accept and execute any received SIMD coprocessor instructions intended for it.

Data may be received via wireless interface 169 for processing by the SIMD coprocessor instructions. For one example, voice communication may be received in the form of a digital signal, which may be processed by the SIMD coprocessor instructions to regenerate digital audio samples representative of the voice communications. For another example, compressed audio and/or video may be received in the form of a digital bit stream, which may be processed by the SIMD coprocessor instructions to regenerate digital audio samples and/or motion video frames. In one embodiment of processing core 170, main processor 166, and a SIMD coprocessor 161 may be integrated into a single processing core 170 comprising an execution unit 162, a set of register files 164, and a decoder 165 to recognize instructions of instruction set 163 including instructions in accordance with one embodiment.

FIG. 2 is a block diagram of the micro-architecture for a processor 200 that may include logic circuits to perform instructions, in accordance with embodiments of the present disclosure. In some embodiments, an instruction in accordance with one embodiment may be implemented to operate on data elements having sizes of byte, word, doubleword, quadword, etc., as well as datatypes, such as single and double precision integer and floating point datatypes. In one embodiment, in-order front end 201 may implement a part of processor 200 that may fetch instructions to be executed and prepares the instructions to be used later in the processor pipeline. Front end 201 may include several units. In one embodiment, instruction prefetcher 226 fetches instructions from memory and feeds the instructions to an instruction decoder 228 which in turn decodes or interprets the instructions. For example, in one embodiment, the decoder decodes a received instruction into one or more operations called “micro-instructions” or “micro-operations” (also called micro op or uops) that the machine may execute. In other embodiments, the decoder parses the instruction into an opcode and corresponding data and control fields that may be used by the micro-architecture to perform operations in accordance with one embodiment. In one embodiment, trace cache 230 may assemble decoded uops into program ordered sequences or traces in uop queue 234 for execution. When trace cache 230 encounters a complex instruction, microcode ROM 232 provides the uops needed to complete the operation.

Some instructions may be converted into a single micro-op, whereas others need several micro-ops to complete the full operation. In one embodiment, if more than four micro-ops are needed to complete an instruction, decoder 228 may access microcode ROM 232 to perform the instruction. In one embodiment, an instruction may be decoded into a small number of micro-ops for processing at instruction decoder 228. In another embodiment, an instruction may be stored within microcode ROM 232 should a number of micro-ops be needed to accomplish the operation. Trace cache 230 refers to an entry point programmable logic array (PLA) to determine a correct micro-instruction pointer for reading the micro-code sequences to complete one or more instructions in accordance with one embodiment from micro-code ROM 232. After microcode ROM 232 finishes sequencing micro-ops for an instruction, front end 201 of the machine may resume fetching micro-ops from trace cache 230.

Out-of-order execution engine 203 may prepare instructions for execution. The out-of-order execution logic has a number of buffers to smooth out and re-order the flow of instructions to optimize performance as they go down the pipeline and get scheduled for execution. The allocator logic allocates the machine buffers and resources that each uop needs in order to execute. The register renaming logic renames logic registers onto entries in a register file. The allocator also allocates an entry for each uop in one of the two uop queues, one for memory operations and one for non-memory operations, in front of the instruction schedulers: memory scheduler, fast scheduler 202, slow/general floating point scheduler 204, and simple floating point scheduler 206. Uop schedulers 202, 204, 206, determine when a uop is ready to execute based on the readiness of their dependent input register operand sources and the availability of the execution resources the uops need to complete their operation. Fast scheduler 202 of one embodiment may schedule on each half of the main clock cycle while the other schedulers may only schedule once per main processor clock cycle. The schedulers arbitrate for the dispatch ports to schedule uops for execution.

Register files 208, 210 may be arranged between schedulers 202, 204, 206, and execution units 212, 214, 216, 218, 220, 222, 224 in execution block 211. Each of register files 208, 210 perform integer and floating point operations, respectively. Each register file 208, 210, may include a bypass network that may bypass or forward just completed results that have not yet been written into the register file to new dependent uops. Integer register file 208 and floating point register file 210 may communicate data with the other. In one embodiment, integer register file 208 may be split into two separate register files, one register file for low-order thirty-two bits of data and a second register file for high order thirty-two bits of data. Floating point register file 210 may include 128-bit wide entries because floating point instructions typically have operands from 64 to 128 bits in width.

Execution block 211 may contain execution units 212, 214, 216, 218, 220, 222, 224. Execution units 212, 214, 216, 218, 220, 222, 224 may execute the instructions. Execution block 211 may include register files 208, 210 that store the integer and floating point data operand values that the micro-instructions need to execute. In one embodiment, processor 200 may comprise a number of execution units: address generation unit (AGU) 212, AGU 214, fast Arithmetic Logic Unit (ALU) 216, fast ALU 218, slow ALU 220, floating point ALU 222, floating point move unit 224. In another embodiment, floating point execution blocks 222, 224, may execute floating point, MMX, SIMD, and SSE, or other operations. In yet another embodiment, floating point ALU 222 may include a 64-bit by 64-bit floating point divider to execute divide, square root, and remainder micro-ops. In various embodiments, instructions involving a floating point value may be handled with the floating point hardware. In one embodiment, ALU operations may be passed to high-speed ALU execution units 216, 218. High-speed ALUs 216, 218 may execute fast operations with an effective latency of half a clock cycle. In one embodiment, most complex integer operations go to slow ALU 220 as slow ALU 220 may include integer execution hardware for long-latency type of operations, such as a multiplier, shifts, flag logic, and branch processing. Memory load/store operations may be executed by AGUs 212, 214. In one embodiment, integer ALUs 216, 218, 220 may perform integer operations on 64-bit data operands. In other embodiments, ALUs 216, 218, 220 may be implemented to support a variety of data bit sizes including sixteen, thirty-two, 128, 256, etc. Similarly, floating point units 222, 224 may be implemented to support a range of operands having bits of various widths. In one embodiment, floating point units 222, 224, may operate on 128-bit wide packed data operands in conjunction with SIMD and multimedia instructions.

In one embodiment, uops schedulers 202, 204, 206, dispatch dependent operations before the parent load has finished executing. As uops may be speculatively scheduled and executed in processor 200, processor 200 may also include logic to handle memory misses. If a data load misses in the data cache, there may be dependent operations in flight in the pipeline that have left the scheduler with temporarily incorrect data. A replay mechanism tracks and re-executes instructions that use incorrect data. Only the dependent operations might need to be replayed and the independent ones may be allowed to complete. The schedulers and replay mechanism of one embodiment of a processor may also be designed to catch instruction sequences for text string comparison operations.

The term “registers” may refer to the on-board processor storage locations that may be used as part of instructions to identify operands. In other words, registers may be those that may be usable from the outside of the processor (from a programmer's perspective). However, in some embodiments registers might not be limited to a particular type of circuit. Rather, a register may store data, provide data, and perform the functions described herein. The registers described herein may be implemented by circuitry within a processor using any number of different techniques, such as dedicated physical registers, dynamically allocated physical registers using register renaming, combinations of dedicated and dynamically allocated physical registers, etc. In one embodiment, integer registers store 32-bit integer data. A register file of one embodiment also contains eight multimedia SIMD registers for packed data. For the discussions below, the registers may be understood to be data registers designed to hold packed data, such as 64-bit wide MMX™ registers (also referred to as ‘mm’ registers in some instances) in microprocessors enabled with MMX technology from Intel Corporation of Santa Clara, Calif. These MMX registers, available in both integer and floating point forms, may operate with packed data elements that accompany SIMD and SSE instructions. Similarly, 128-bit wide XMM registers relating to SSE2, SSE3, SSE4, or beyond (referred to generically as “SSEx”) technology may hold such packed data operands. In one embodiment, in storing packed data and integer data, the registers do not need to differentiate between the two data types. In one embodiment, integer and floating point may be contained in the same register file or different register files. Furthermore, in one embodiment, floating point and integer data may be stored in different registers or the same registers.

In the examples of the following figures, a number of data operands may be described. FIG. 3A illustrates various packed data type representations in multimedia registers, in accordance with embodiments of the present disclosure. FIG. 3A illustrates data types for a packed byte 310, a packed word 320, and a packed doubleword (dword) 330 for 128-bit wide operands. Packed byte format 310 of this example may be 128 bits long and contains sixteen packed byte data elements. A byte may be defined, for example, as eight bits of data. Information for each byte data element may be stored in bit 7 through bit 0 for byte 0, bit 15 through bit 8 for byte 1, bit 23 through bit 16 for byte 2, and finally bit 120 through bit 127 for byte 15. Thus, all available bits may be used in the register. This storage arrangement increases the storage efficiency of the processor. As well, with sixteen data elements accessed, one operation may now be performed on sixteen data elements in parallel.

Generally, a data element may include an individual piece of data that is stored in a single register or memory location with other data elements of the same length. In packed data sequences relating to SSEx technology, the number of data elements stored in a XMM register may be 128 bits divided by the length in bits of an individual data element. Similarly, in packed data sequences relating to MMX and SSE technology, the number of data elements stored in an MMX register may be 64 bits divided by the length in bits of an individual data element. Although the data types illustrated in FIG. 3A may be 128 bits long, embodiments of the present disclosure may also operate with 64-bit wide or other sized operands. Packed word format 320 of this example may be 128 bits long and contains eight packed word data elements. Each packed word contains sixteen bits of information. Packed doubleword format 330 of FIG. 3A may be 128 bits long and contains four packed doubleword data elements. Each packed doubleword data element contains thirty-two bits of information. A packed quadword may be 128 bits long and contain two packed quad-word data elements.

FIG. 3B illustrates possible in-register data storage formats, in accordance with embodiments of the present disclosure. Each packed data may include more than one independent data element. Three packed data formats are illustrated; packed half 341, packed single 342, and packed double 343. One embodiment of packed half 341, packed single 342, and packed double 343 contain fixed-point data elements. For another embodiment one or more of packed half 341, packed single 342, and packed double 343 may contain floating-point data elements. One embodiment of packed half 341 may be 128 bits long containing eight 16-bit data elements. One embodiment of packed single 342 may be 128 bits long and contains four 32-bit data elements. One embodiment of packed double 343 may be 128 bits long and contains two 64-bit data elements. It will be appreciated that such packed data formats may be further extended to other register lengths, for example, to 96-bits, 160-bits, 192-bits, 224-bits, 256-bits or more.

FIG. 3C illustrates various signed and unsigned packed data type representations in multimedia registers, in accordance with embodiments of the present disclosure. Unsigned packed byte representation 344 illustrates the storage of an unsigned packed byte in a SIMD register. Information for each byte data element may be stored in bit 7 through bit 0 for byte 0, bit 15 through bit 8 for byte 1, bit 23 through bit 16 for byte 2, and finally bit 120 through bit 127 for byte 15. Thus, all available bits may be used in the register. This storage arrangement may increase the storage efficiency of the processor. As well, with sixteen data elements accessed, one operation may now be performed on sixteen data elements in a parallel fashion. Signed packed byte representation 345 illustrates the storage of a signed packed byte. Note that the eighth bit of every byte data element may be the sign indicator. Unsigned packed word representation 346 illustrates how word seven through word zero may be stored in a SIMD register. Signed packed word representation 347 may be similar to the unsigned packed word in-register representation 346. Note that the sixteenth bit of each word data element may be the sign indicator. Unsigned packed doubleword representation 348 shows how doubleword data elements are stored. Signed packed doubleword representation 349 may be similar to unsigned packed doubleword in-register representation 348. Note that the necessary sign bit may be the thirty-second bit of each doubleword data element.

FIG. 3D illustrates an embodiment of an operation encoding (opcode). Furthermore, format 360 may include register/memory operand addressing modes corresponding with a type of opcode format described in the “IA-32 Intel Architecture Software Developer's Manual Volume 2: Instruction Set Reference,” which is available from Intel Corporation, Santa Clara, Calif. on the world-wide-web (www) at intel.com/design/litcentr. In one embodiment, and instruction may be encoded by one or more of fields 361 and 362. Up to two operand locations per instruction may be identified, including up to two source operand identifiers 364 and 365. In one embodiment, destination operand identifier 366 may be the same as source operand identifier 364, whereas in other embodiments they may be different. In another embodiment, destination operand identifier 366 may be the same as source operand identifier 365, whereas in other embodiments they may be different. In one embodiment, one of the source operands identified by source operand identifiers 364 and 365 may be overwritten by the results of the text string comparison operations, whereas in other embodiments identifier 364 corresponds to a source register element and identifier 365 corresponds to a destination register element. In one embodiment, operand identifiers 364 and 365 may identify 32-bit or 64-bit source and destination operands.

FIG. 3E illustrates another possible operation encoding (opcode) format 370, having forty or more bits, in accordance with embodiments of the present disclosure. Opcode format 370 corresponds with opcode format 360 and comprises an optional prefix byte 378. An instruction according to one embodiment may be encoded by one or more of fields 378, 371, and 372. Up to two operand locations per instruction may be identified by source operand identifiers 374 and 375 and by prefix byte 378. In one embodiment, prefix byte 378 may be used to identify 32-bit or 64-bit source and destination operands. In one embodiment, destination operand identifier 376 may be the same as source operand identifier 374, whereas in other embodiments they may be different. For another embodiment, destination operand identifier 376 may be the same as source operand identifier 375, whereas in other embodiments they may be different. In one embodiment, an instruction operates on one or more of the operands identified by operand identifiers 374 and 375 and one or more operands identified by operand identifiers 374 and 375 may be overwritten by the results of the instruction, whereas in other embodiments, operands identified by identifiers 374 and 375 may be written to another data element in another register. Opcode formats 360 and 370 allow register to register, memory to register, register by memory, register by register, register by immediate, register to memory addressing specified in part by MOD fields 363 and 373 and by optional scale-index-base and displacement bytes.

FIG. 3F illustrates yet another possible operation encoding (opcode) format, in accordance with embodiments of the present disclosure. 64-bit single instruction multiple data (SIMD) arithmetic operations may be performed through a coprocessor data processing (CDP) instruction. Operation encoding (opcode) format 380 depicts one such CDP instruction having CDP opcode fields 382 an0064 389. The type of CDP instruction, for another embodiment, operations may be encoded by one or more of fields 383, 384, 387, and 388. Up to three operand locations per instruction may be identified, including up to two source operand identifiers 385 and 390 and one destination operand identifier 386. One embodiment of the coprocessor may operate on eight, sixteen, thirty-two, and 64-bit values. In one embodiment, an instruction may be performed on integer data elements. In some embodiments, an instruction may be executed conditionally, using condition field 381. For some embodiments, source data sizes may be encoded by field 383. In some embodiments, Zero (Z), negative (N), carry (C), and overflow (V) detection may be done on SIMD fields. For some instructions, the type of saturation may be encoded by field 384.

FIG. 4A is a block diagram illustrating an in-order pipeline and a register renaming stage, out-of-order issue/execution pipeline, in accordance with embodiments of the present disclosure. FIG. 4B is a block diagram illustrating an in-order architecture core and a register renaming logic, out-of-order issue/execution logic to be included in a processor, in accordance with embodiments of the present disclosure. The solid lined boxes in FIG. 4A illustrate the in-order pipeline, while the dashed lined boxes illustrates the register renaming, out-of-order issue/execution pipeline. Similarly, the solid lined boxes in FIG. 4B illustrate the in-order architecture logic, while the dashed lined boxes illustrates the register renaming logic and out-of-order issue/execution logic.

In FIG. 4A, a processor pipeline 400 may include a fetch stage 402, a length decode stage 404, a decode stage 406, an allocation stage 408, a renaming stage 410, a scheduling (also known as a dispatch or issue) stage 412, a register read/memory read stage 414, an execute stage 416, a write-back/memory-write stage 418, an exception handling stage 422, and a commit stage 424.

In FIG. 4B, arrows denote a coupling between two or more units and the direction of the arrow indicates a direction of data flow between those units. FIG. 4B shows processor core 490 including a front end unit 430 coupled to an execution engine unit 450, and both may be coupled to a memory unit 470.

Core 490 may be a Reduced Instruction Set Computing (RISC) core, a Complex Instruction Set Computing (CISC) core, a Very Long Instruction Word (VLIW) core, or a hybrid or alternative core type. In one embodiment, core 490 may be a special-purpose core, such as, for example, a network or communication core, compression engine, graphics core, or the like.

Front end unit 430 may include a branch prediction unit 432 coupled to an instruction cache unit 434. Instruction cache unit 434 may be coupled to an instruction Translation Lookaside Buffer (TLB) 436. TLB 436 may be coupled to an instruction fetch unit 438, which is coupled to a decode unit 440. Decode unit 440 may decode instructions, and generate as an output one or more micro-operations, micro-code entry points, microinstructions, other instructions, or other control signals, which may be decoded from, or which otherwise reflect, or may be derived from, the original instructions. The decoder may be implemented using various different mechanisms. Examples of suitable mechanisms include, but are not limited to, look-up tables, hardware implementations, programmable logic arrays (PLAs), microcode read-only memories (ROMs), etc. In one embodiment, instruction cache unit 434 may be further coupled to a level 2 (L2) cache unit 476 in memory unit 470. Decode unit 440 may be coupled to a rename/allocator unit 452 in execution engine unit 450.

Execution engine unit 450 may include rename/allocator unit 452 coupled to a retirement unit 454 and a set of one or more scheduler units 456. Scheduler units 456 represent any number of different schedulers, including reservations stations, central instruction window, etc. Scheduler units 456 may be coupled to physical register file units 458. Each of physical register file units 458 represents one or more physical register files, different ones of which store one or more different data types, such as scalar integer, scalar floating point, packed integer, packed floating point, vector integer, vector floating point, etc., status (e.g., an instruction pointer that is the address of the next instruction to be executed), etc. Physical register file units 458 may be overlapped by retirement unit 154 to illustrate various ways in which register renaming and out-of-order execution may be implemented (e.g., using one or more reorder buffers and one or more retirement register files, using one or more future files, one or more history buffers, and one or more retirement register files; using register maps and a pool of registers; etc.). Generally, the architectural registers may be visible from the outside of the processor or from a programmer's perspective. The registers might not be limited to any known particular type of circuit. Various different types of registers may be suitable as long as they store and provide data as described herein. Examples of suitable registers include, but might not be limited to, dedicated physical registers, dynamically allocated physical registers using register renaming, combinations of dedicated and dynamically allocated physical registers, etc. Retirement unit 454 and physical register file units 458 may be coupled to execution clusters 460. Execution clusters 460 may include a set of one or more execution units 162 and a set of one or more memory access units 464. Execution units 462 may perform various operations (e.g., shifts, addition, subtraction, multiplication) and on various types of data (e.g., scalar floating point, packed integer, packed floating point, vector integer, vector floating point). While some embodiments may include a number of execution units dedicated to specific functions or sets of functions, other embodiments may include only one execution unit or multiple execution units that all perform all functions. Scheduler units 456, physical register file units 458, and execution clusters 460 are shown as being possibly plural because certain embodiments create separate pipelines for certain types of data/operations (e.g., a scalar integer pipeline, a scalar floating point/packed integer/packed floating point/vector integer/vector floating point pipeline, and/or a memory access pipeline that each have their own scheduler unit, physical register file unit, and/or execution cluster—and in the case of a separate memory access pipeline, certain embodiments may be implemented in which only the execution cluster of this pipeline has memory access units 464). It should also be understood that where separate pipelines are used, one or more of these pipelines may be out-of-order issue/execution and the rest in-order.

The set of memory access units 464 may be coupled to memory unit 470, which may include a data TLB unit 472 coupled to a data cache unit 474 coupled to a level 2 (L2) cache unit 476. In one exemplary embodiment, memory access units 464 may include a load unit, a store address unit, and a store data unit, each of which may be coupled to data TLB unit 472 in memory unit 470. L2 cache unit 476 may be coupled to one or more other levels of cache and eventually to a main memory.

By way of example, the exemplary register renaming, out-of-order issue/execution core architecture may implement pipeline 400 as follows: 1) instruction fetch 438 may perform fetch and length decoding stages 402 and 404; 2) decode unit 440 may perform decode stage 406; 3) rename/allocator unit 452 may perform allocation stage 408 and renaming stage 410; 4) scheduler units 456 may perform schedule stage 412; 5) physical register file units 458 and memory unit 470 may perform register read/memory read stage 414; execution cluster 460 may perform execute stage 416; 6) memory unit 470 and physical register file units 458 may perform write-back/memory-write stage 418; 7) various units may be involved in the performance of exception handling stage 422; and 8) retirement unit 454 and physical register file units 458 may perform commit stage 424.

Core 490 may support one or more instructions sets (e.g., the x86 instruction set (with some extensions that have been added with newer versions); the MIPS instruction set of MIPS Technologies of Sunnyvale, Calif.; the ARM instruction set (with optional additional extensions such as NEON) of ARM Holdings of Sunnyvale, Calif.).

It should be understood that the core may support multithreading (executing two or more parallel sets of operations or threads) in a variety of manners. Multithreading support may be performed by, for example, including time sliced multithreading, simultaneous multithreading (where a single physical core provides a logical core for each of the threads that physical core is simultaneously multithreading), or a combination thereof. Such a combination may include, for example, time sliced fetching and decoding and simultaneous multithreading thereafter such as in the Intel® Hyperthreading technology.

While register renaming may be described in the context of out-of-order execution, it should be understood that register renaming may be used in an in-order architecture. While the illustrated embodiment of the processor may also include a separate instruction and data cache units 434/474 and a shared L2 cache unit 476, other embodiments may have a single internal cache for both instructions and data, such as, for example, a Level 1 (L1) internal cache, or multiple levels of internal cache. In some embodiments, the system may include a combination of an internal cache and an external cache that may be external to the core and/or the processor. In other embodiments, all of the cache may be external to the core and/or the processor.

FIG. 5A is a block diagram of a processor 500, in accordance with embodiments of the present disclosure. In one embodiment, processor 500 may include a multicore processor. Processor 500 may include a system agent 510 communicatively coupled to one or more cores 502. Furthermore, cores 502 and system agent 510 may be communicatively coupled to one or more caches 506. Cores 502, system agent 510, and caches 506 may be communicatively coupled via one or more memory control units 552. Furthermore, cores 502, system agent 510, and caches 506 may be communicatively coupled to a graphics module 560 via memory control units 552.

Processor 500 may include any suitable mechanism for interconnecting cores 502, system agent 510, and caches 506, and graphics module 560. In one embodiment, processor 500 may include a ring-based interconnect unit 508 to interconnect cores 502, system agent 510, and caches 506, and graphics module 560. In other embodiments, processor 500 may include any number of well-known techniques for interconnecting such units. Ring-based interconnect unit 508 may utilize memory control units 552 to facilitate interconnections.

Processor 500 may include a memory hierarchy comprising one or more levels of caches within the cores, one or more shared cache units such as caches 506, or external memory (not shown) coupled to the set of integrated memory controller units 552. Caches 506 may include any suitable cache. In one embodiment, caches 506 may include one or more mid-level caches, such as Level 2 (L2), Level 3 (L3), Level 4 (L4), or other levels of cache, a last level cache (LLC), and/or combinations thereof.

In various embodiments, one or more of cores 502 may perform multithreading. System agent 510 may include components for coordinating and operating cores 502. System agent unit 510 may include for example a Power Control Unit (PCU). The PCU may be or include logic and components needed for regulating the power state of cores 502. System agent 510 may include a display engine 512 for driving one or more externally connected displays or graphics module 560. System agent 510 may include an interface 1214 for communications busses for graphics. In one embodiment, interface 1214 may be implemented by PCI Express (PCIe). In a further embodiment, interface 1214 may be implemented by PCI Express Graphics (PEG). System agent 510 may include a direct media interface (DMI) 516. DMI 516 may provide links between different bridges on a motherboard or other portion of a computer system. System agent 510 may include a PCIe bridge 1218 for providing PCIe links to other elements of a computing system. PCIe bridge 1218 may be implemented using a memory controller 1220 and coherence logic 1222.

Cores 502 may be implemented in any suitable manner. Cores 502 may be homogenous or heterogeneous in terms of architecture and/or instruction set. In one embodiment, some of cores 502 may be in-order while others may be out-of-order. In another embodiment, two or more of cores 502 may execute the same instruction set, while others may execute only a subset of that instruction set or a different instruction set.

Processor 500 may include a general-purpose processor, such as a Core™ i3, i5, i7, 2 Duo and Quad, Xeon™, Itanium™, XScale™ or StrongARM™ processor, which may be available from Intel Corporation, of Santa Clara, Calif. Processor 500 may be provided from another company, such as ARM Holdings, Ltd, MIPS, etc. Processor 500 may be a special-purpose processor, such as, for example, a network or communication processor, compression engine, graphics processor, co-processor, embedded processor, or the like. Processor 500 may be implemented on one or more chips. Processor 500 may be a part of and/or may be implemented on one or more substrates using any of a number of process technologies, such as, for example, BiCMOS, CMOS, or NMOS.

In one embodiment, a given one of caches 506 may be shared by multiple ones of cores 502. In another embodiment, a given one of caches 506 may be dedicated to one of cores 502. The assignment of caches 506 to cores 502 may be handled by a cache controller or other suitable mechanism. A given one of caches 506 may be shared by two or more cores 502 by implementing time-slices of a given cache 506.

Graphics module 560 may implement an integrated graphics processing subsystem. In one embodiment, graphics module 560 may include a graphics processor. Furthermore, graphics module 560 may include a media engine 565. Media engine 565 may provide media encoding and video decoding.

FIG. 5B is a block diagram of an example implementation of a core 502, in accordance with embodiments of the present disclosure. Core 502 may include a front end 570 communicatively coupled to an out-of-order engine 580. Core 502 may be communicatively coupled to other portions of processor 500 through cache hierarchy 503.

Front end 570 may be implemented in any suitable manner, such as fully or in part by front end 201 as described above. In one embodiment, front end 570 may communicate with other portions of processor 500 through cache hierarchy 503. In a further embodiment, front end 570 may fetch instructions from portions of processor 500 and prepare the instructions to be used later in the processor pipeline as they are passed to out-of-order execution engine 580.

Out-of-order execution engine 580 may be implemented in any suitable manner, such as fully or in part by out-of-order execution engine 203 as described above. Out-of-order execution engine 580 may prepare instructions received from front end 570 for execution. Out-of-order execution engine 580 may include an allocate module 1282. In one embodiment, allocate module 1282 may allocate resources of processor 500 or other resources, such as registers or buffers, to execute a given instruction. Allocate module 1282 may make allocations in schedulers, such as a memory scheduler, fast scheduler, or floating point scheduler. Such schedulers may be represented in FIG. 5B by resource schedulers 584. Allocate module 1282 may be implemented fully or in part by the allocation logic described in conjunction with FIG. 2. Resource schedulers 584 may determine when an instruction is ready to execute based on the readiness of a given resource's sources and the availability of execution resources needed to execute an instruction. Resource schedulers 584 may be implemented by, for example, schedulers 202, 204, 206 as discussed above. Resource schedulers 584 may schedule the execution of instructions upon one or more resources. In one embodiment, such resources may be internal to core 502, and may be illustrated, for example, as resources 586. In another embodiment, such resources may be external to core 502 and may be accessible by, for example, cache hierarchy 503. Resources may include, for example, memory, caches, register files, or registers. Resources internal to core 502 may be represented by resources 586 in FIG. 5B. As necessary, values written to or read from resources 586 may be coordinated with other portions of processor 500 through, for example, cache hierarchy 503. As instructions are assigned resources, they may be placed into a reorder buffer 588. Reorder buffer 588 may track instructions as they are executed and may selectively reorder their execution based upon any suitable criteria of processor 500. In one embodiment, reorder buffer 588 may identify instructions or a series of instructions that may be executed independently. Such instructions or a series of instructions may be executed in parallel from other such instructions. Parallel execution in core 502 may be performed by any suitable number of separate execution blocks or virtual processors. In one embodiment, shared resources—such as memory, registers, and caches—may be accessible to multiple virtual processors within a given core 502. In other embodiments, shared resources may be accessible to multiple processing entities within processor 500.

Cache hierarchy 503 may be implemented in any suitable manner. For example, cache hierarchy 503 may include one or more lower or mid-level caches, such as caches 572, 574. In one embodiment, cache hierarchy 503 may include an LLC 595 communicatively coupled to caches 572, 574. In another embodiment, LLC 595 may be implemented in a module 590 accessible to all processing entities of processor 500. In a further embodiment, module 590 may be implemented in an uncore module of processors from Intel, Inc. Module 590 may include portions or subsystems of processor 500 necessary for the execution of core 502 but might not be implemented within core 502. Besides LLC 595, Module 590 may include, for example, hardware interfaces, memory coherency coordinators, interprocessor interconnects, instruction pipelines, or memory controllers. Access to RAM 599 available to processor 500 may be made through module 590 and, more specifically, LLC 595. Furthermore, other instances of core 502 may similarly access module 590. Coordination of the instances of core 502 may be facilitated in part through module 590.

FIGS. 6-8 may illustrate exemplary systems suitable for including processor 500, while FIG. 9 may illustrate an exemplary System on a Chip (SoC) that may include one or more of cores 502. Other system designs and implementations known in the arts for laptops, desktops, handheld PCs, personal digital assistants, engineering workstations, servers, network devices, network hubs, switches, embedded processors, DSPs, graphics devices, video game devices, set-top boxes, micro controllers, cell phones, portable media players, hand held devices, and various other electronic devices, may also be suitable. In general, a huge variety of systems or electronic devices that incorporate a processor and/or other execution logic as disclosed herein may be generally suitable.

FIG. 6 illustrates a block diagram of a system 600, in accordance with embodiments of the present disclosure. System 600 may include one or more processors 610, 615, which may be coupled to Graphics Memory Controller Hub (GMCH) 620. The optional nature of additional processors 615 is denoted in FIG. 6 with broken lines.

Each processor 610,615 may be some version of processor 500. However, it should be noted that integrated graphics logic and integrated memory control units might not exist in processors 610,615. FIG. 6 illustrates that GMCH 620 may be coupled to a memory 640 that may be, for example, a dynamic random access memory (DRAM). The DRAM may, for at least one embodiment, be associated with a non-volatile cache.

GMCH 620 may be a chipset, or a portion of a chipset. GMCH 620 may communicate with processors 610, 615 and control interaction between processors 610, 615 and memory 640. GMCH 620 may also act as an accelerated bus interface between the processors 610, 615 and other elements of system 600. In one embodiment, GMCH 620 communicates with processors 610, 615 via a multi-drop bus, such as a frontside bus (FSB) 695.

Furthermore, GMCH 620 may be coupled to a display 645 (such as a flat panel display). In one embodiment, GMCH 620 may include an integrated graphics accelerator. GMCH 620 may be further coupled to an input/output (I/O) controller hub (ICH) 650, which may be used to couple various peripheral devices to system 600. External graphics device 660 may include be a discrete graphics device coupled to ICH 650 along with another peripheral device 670.

In other embodiments, additional or different processors may also be present in system 600. For example, additional processors 610, 615 may include additional processors that may be the same as processor 610, additional processors that may be heterogeneous or asymmetric to processor 610, accelerators (such as, e.g., graphics accelerators or digital signal processing (DSP) units), field programmable gate arrays, or any other processor. There may be a variety of differences between the physical resources 610, 615 in terms of a spectrum of metrics of merit including architectural, micro-architectural, thermal, power consumption characteristics, and the like. These differences may effectively manifest themselves as asymmetry and heterogeneity amongst processors 610, 615. For at least one embodiment, various processors 610, 615 may reside in the same die package.

FIG. 7 illustrates a block diagram of a second system 700, in accordance with embodiments of the present disclosure. As shown in FIG. 7, multiprocessor system 700 may include a point-to-point interconnect system, and may include a first processor 770 and a second processor 780 coupled via a point-to-point interconnect 750. Each of processors 770 and 780 may be some version of processor 500 as one or more of processors 610,615.

While FIG. 7 may illustrate two processors 770, 780, it is to be understood that the scope of the present disclosure is not so limited. In other embodiments, one or more additional processors may be present in a given processor.

Processors 770 and 780 are shown including integrated memory controller units 772 and 782, respectively. Processor 770 may also include as part of its bus controller units point-to-point (P-P) interfaces 776 and 778; similarly, second processor 780 may include P-P interfaces 786 and 788. Processors 770, 780 may exchange information via a point-to-point (P-P) interface 750 using P-P interface circuits 778, 788. As shown in FIG. 7, IMCs 772 and 782 may couple the processors to respective memories, namely a memory 732 and a memory 734, which in one embodiment may be portions of main memory locally attached to the respective processors.

Processors 770, 780 may each exchange information with a chipset 790 via individual P-P interfaces 752, 754 using point to point interface circuits 776, 794, 786, 798. In one embodiment, chipset 790 may also exchange information with a high-performance graphics circuit 738 via a high-performance graphics interface 739.

A shared cache (not shown) may be included in either processor or outside of both processors, yet connected with the processors via P-P interconnect, such that either or both processors' local cache information may be stored in the shared cache if a processor is placed into a low power mode.

Chipset 790 may be coupled to a first bus 716 via an interface 796. In one embodiment, first bus 716 may be a Peripheral Component Interconnect (PCI) bus, or a bus such as a PCI Express bus or another third generation I/O interconnect bus, although the scope of the present disclosure is not so limited.

As shown in FIG. 7, various I/O devices 714 may be coupled to first bus 716, along with a bus bridge 718 which couples first bus 716 to a second bus 720. In one embodiment, second bus 720 may be a Low Pin Count (LPC) bus. Various devices may be coupled to second bus 720 including, for example, a keyboard and/or mouse 722, communication devices 727 and a storage unit 728 such as a disk drive or other mass storage device which may include instructions/code and data 730, in one embodiment. Further, an audio I/O 724 may be coupled to second bus 720. Note that other architectures may be possible. For example, instead of the point-to-point architecture of FIG. 7, a system may implement a multi-drop bus or other such architecture.

FIG. 8 illustrates a block diagram of a third system 800 in accordance with embodiments of the present disclosure. Like elements in FIGS. 7 and 8 bear like reference numerals, and certain aspects of FIG. 7 have been omitted from FIG. 8 in order to avoid obscuring other aspects of FIG. 8.

FIG. 8 illustrates that processors 870, 880 may include integrated memory and I/O Control Logic (“CL”) 872 and 882, respectively. For at least one embodiment, CL 872, 882 may include integrated memory controller units such as that described above in connection with FIGS. 5 and 7. In addition. CL 872, 882 may also include I/O control logic. FIG. 8 illustrates that not only memories 832, 834 may be coupled to CL 872, 882, but also that I/O devices 814 may also be coupled to control logic 872, 882. Legacy I/O devices 815 may be coupled to chipset 890.

FIG. 9 illustrates a block diagram of a SoC 900, in accordance with embodiments of the present disclosure. Similar elements in FIG. 5 bear like reference numerals. Also, dashed lined boxes may represent optional features on more advanced SoCs. An interconnect units 902 may be coupled to: an application processor 910 which may include a set of one or more cores 902A-N and shared cache units 906; a system agent unit 910; a bus controller units 916; an integrated memory controller units 914; a set or one or more media processors 920 which may include integrated graphics logic 908, an image processor 924 for providing still and/or video camera functionality, an audio processor 926 for providing hardware audio acceleration, and a video processor 928 for providing video encode/decode acceleration; an SRAM unit 930; a DMA unit 932; and a display unit 940 for coupling to one or more external displays.

FIG. 10 illustrates a processor containing a Central Processing Unit (CPU) and a graphics processing unit (GPU), which may perform at least one instruction, in accordance with embodiments of the present disclosure. In one embodiment, an instruction to perform operations according to at least one embodiment could be performed by the CPU. In another embodiment, the instruction could be performed by the GPU. In still another embodiment, the instruction may be performed through a combination of operations performed by the GPU and the CPU. For example, in one embodiment, an instruction in accordance with one embodiment may be received and decoded for execution on the GPU. However, one or more operations within the decoded instruction may be performed by a CPU and the result returned to the GPU for final retirement of the instruction. Conversely, in some embodiments, the CPU may act as the primary processor and the GPU as the co-processor.

In some embodiments, instructions that benefit from highly parallel, throughput processors may be performed by the GPU, while instructions that benefit from the performance of processors that benefit from deeply pipelined architectures may be performed by the CPU. For example, graphics, scientific applications, financial applications and other parallel workloads may benefit from the performance of the GPU and be executed accordingly, whereas more sequential applications, such as operating system kernel or application code may be better suited for the CPU.

In FIG. 10, processor 1000 includes a CPU 1005, GPU 1010, image processor 1015, video processor 1020, USB controller 1025, UART controller 1030, SPI/SDIO controller 1035, display device 1040, memory interface controller 1045, MIPI controller 1050, flash memory controller 1055, Dual Data Rate (DDR) controller 1060, security engine 1065, and I²S/I²C controller 1070. Other logic and circuits may be included in the processor of FIG. 10, including more CPUs or GPUs and other peripheral interface controllers.

One or more aspects of at least one embodiment may be implemented by representative data stored on a machine-readable medium which represents various logic within the processor, which when read by a machine causes the machine to fabricate logic to perform the techniques described herein. Such representations, known as “IP cores” may be stored on a tangible, machine-readable medium (“tape”) and supplied to various customers or manufacturing facilities to load into the fabrication machines that actually make the logic or processor. For example, IP cores, such as the Cortex™ family of processors developed by ARM Holdings, Ltd. and Loongson IP cores developed the Institute of Computing Technology (ICT) of the Chinese Academy of Sciences may be licensed or sold to various customers or licensees, such as Texas Instruments, Qualcomm, Apple, or Samsung and implemented in processors produced by these customers or licensees.

FIG. 11 illustrates a block diagram illustrating the development of IP cores, in accordance with embodiments of the present disclosure. Storage 1130 may include simulation software 1120 and/or hardware or software model 1110. In one embodiment, the data representing the IP core design may be provided to storage 1130 via memory 1140 (e.g., hard disk), wired connection (e.g., internet) 1150 or wireless connection 1160. The IP core information generated by the simulation tool and model may then be transmitted to a fabrication facility where it may be fabricated by a third party to perform at least one instruction in accordance with at least one embodiment.

In some embodiments, one or more instructions may correspond to a first type or architecture (e.g., x86) and be translated or emulated on a processor of a different type or architecture (e.g., ARM). An instruction, according to one embodiment, may therefore be performed on any processor or processor type, including ARM, x86, MIPS, a GPU, or other processor type or architecture.

FIG. 12 illustrates how an instruction of a first type may be emulated by a processor of a different type, in accordance with embodiments of the present disclosure. In FIG. 12, program 1205 contains some instructions that may perform the same or substantially the same function as an instruction according to one embodiment. However the instructions of program 1205 may be of a type and/or format that is different from or incompatible with processor 1215, meaning the instructions of the type in program 1205 may not be able to execute natively by the processor 1215. However, with the help of emulation logic, 1210, the instructions of program 1205 may be translated into instructions that may be natively be executed by the processor 1215. In one embodiment, the emulation logic may be embodied in hardware. In another embodiment, the emulation logic may be embodied in a tangible, machine-readable medium containing software to translate instructions of the type in program 1205 into the type natively executable by processor 1215. In other embodiments, emulation logic may be a combination of fixed-function or programmable hardware and a program stored on a tangible, machine-readable medium. In one embodiment, the processor contains the emulation logic, whereas in other embodiments, the emulation logic exists outside of the processor and may be provided by a third party. In one embodiment, the processor may load the emulation logic embodied in a tangible, machine-readable medium containing software by executing microcode or firmware contained in or associated with the processor.

FIG. 13 illustrates a block diagram contrasting the use of a software instruction converter to convert binary instructions in a source instruction set to binary instructions in a target instruction set, in accordance with embodiments of the present disclosure. In the illustrated embodiment, the instruction converter may be a software instruction converter, although the instruction converter may be implemented in software, firmware, hardware, or various combinations thereof. FIG. 13 shows a program in a high level language 1302 may be compiled using an x86 compiler 1304 to generate x86 binary code 1306 that may be natively executed by a processor with at least one x86 instruction set core 1316. The processor with at least one x86 instruction set core 1316 represents any processor that may perform substantially the same functions as an Intel processor with at least one x86 instruction set core by compatibly executing or otherwise processing (1) a substantial portion of the instruction set of the Intel x86 instruction set core or (2) object code versions of applications or other software targeted to run on an Intel processor with at least one x86 instruction set core, in order to achieve substantially the same result as an Intel processor with at least one x86 instruction set core. x86 compiler 1304 represents a compiler that may be operable to generate x86 binary code 1306 (e.g., object code) that may, with or without additional linkage processing, be executed on the processor with at least one x86 instruction set core 1316. Similarly, FIG. 13 shows the program in high level language 1302 may be compiled using an alternative instruction set compiler 1308 to generate alternative instruction set binary code 1310 that may be natively executed by a processor without at least one x86 instruction set core 1314 (e.g., a processor with cores that execute the MIPS instruction set of MIPS Technologies of Sunnyvale, Calif. and/or that execute the ARM instruction set of ARM Holdings of Sunnyvale, Calif.). Instruction converter 1312 may be used to convert x86 binary code 1306 into code that may be natively executed by the processor without an x86 instruction set core 1314. This converted code might not be the same as alternative instruction set binary code 1310; however, the converted code will accomplish the general operation and be made up of instructions from the alternative instruction set. Thus, instruction converter 1312 represents software, firmware, hardware, or a combination thereof that, through emulation, simulation or any other process, allows a processor or other electronic device that does not have an x86 instruction set processor or core to execute x86 binary code 1306.

FIG. 14 is a block diagram of an instruction set architecture 1400 of a processor, in accordance with embodiments of the present disclosure. Instruction set architecture 1400 may include any suitable number or kind of components.

For example, instruction set architecture 1400 may include processing entities such as one or more cores 1406, 1407 and a graphics processing unit 1415. Cores 1406, 1407 may be communicatively coupled to the rest of instruction set architecture 1400 through any suitable mechanism, such as through a bus or cache. In one embodiment, cores 1406, 1407 may be communicatively coupled through an L2 cache control 1408, which may include a bus interface unit 1409 and an L2 cache 1410. Cores 1406, 1407 and graphics processing unit 1415 may be communicatively coupled to each other and to the remainder of instruction set architecture 1400 through interconnect 1410. In one embodiment, graphics processing unit 1415 may use a video code 1420 defining the manner in which particular video signals will be encoded and decoded for output.

Instruction set architecture 1400 may also include any number or kind of interfaces, controllers, or other mechanisms for interfacing or communicating with other portions of an electronic device or system. Such mechanisms may facilitate interaction with, for example, peripherals, communications devices, other processors, or memory. In the example of FIG. 14, instruction set architecture 1400 may include an LCD video interface 1425, a Subscriber Interface Module (SIM) interface 1430, a boot ROM interface 1435, an SDRAM controller 1440, a flash controller 1445, and a Serial Peripheral Interface (SPI) master unit 1450. LCD video interface 1425 may provide output of video signals from, for example, GPU 1415 and through, for example, a Mobile Industry Processor Interface (MIPI) 1490 or a High-Definition Multimedia Interface (HDMI) 1495 to a display. Such a display may include, for example, an LCD. SIM interface 1430 may provide access to or from a SIM card or device. SDRAM controller 1440 may provide access to or from memory such as an SDRAM chip or module. Flash controller 1445 may provide access to or from memory such as flash memory or other instances of RAM. SPI master unit 1450 may provide access to or from communications modules, such as a Bluetooth module 1470, high-speed 3G modem 1475, global positioning system module 1480, or wireless module 1485 implementing a communications standard such as 802.11.

FIG. 15 is a more detailed block diagram of an instruction set architecture 1500 of a processor, in accordance with embodiments of the present disclosure. Instruction architecture 1500 may implement one or more aspects of instruction set architecture 1400. Furthermore, instruction set architecture 1500 may illustrate modules and mechanisms for the execution of instructions within a processor.

Instruction architecture 1500 may include a memory system 1540 communicatively coupled to one or more execution entities 1565. Furthermore, instruction architecture 1500 may include a caching and bus interface unit such as unit 1510 communicatively coupled to execution entities 1565 and memory system 1540. In one embodiment, loading of instructions into execution entities 1564 may be performed by one or more stages of execution. Such stages may include, for example, instruction prefetch stage 1530, dual instruction decode stage 1550, register rename stage 155, issue stage 1560, and writeback stage 1570.

In one embodiment, memory system 1540 may include an executed instruction pointer 1580. Executed instruction pointer 1580 may store a value identifying the oldest, undispatched instruction within a batch of instructions. The oldest instruction may correspond to the lowest Program Order (PO) value. A PO may include a unique number of an instruction. Such an instruction may be a single instruction within a thread represented by multiple strands. A PO may be used in ordering instructions to ensure correct execution semantics of code. A PO may be reconstructed by mechanisms such as evaluating increments to PO encoded in the instruction rather than an absolute value. Such a reconstructed PO may be known as an “RPO.” Although a PO may be referenced herein, such a PO may be used interchangeably with an RPO. A strand may include a sequence of instructions that are data dependent upon each other. The strand may be arranged by a binary translator at compilation time. Hardware executing a strand may execute the instructions of a given strand in order according to PO of the various instructions. A thread may include multiple strands such that instructions of different strands may depend upon each other. A PO of a given strand may be the PO of the oldest instruction in the strand which has not yet been dispatched to execution from an issue stage. Accordingly, given a thread of multiple strands, each strand including instructions ordered by PO, executed instruction pointer 1580 may store the oldest—illustrated by the lowest number—PO in the thread.

In another embodiment, memory system 1540 may include a retirement pointer 1582. Retirement pointer 1582 may store a value identifying the PO of the last retired instruction. Retirement pointer 1582 may be set by, for example, retirement unit 454. If no instructions have yet been retired, retirement pointer 1582 may include a null value.

Execution entities 1565 may include any suitable number and kind of mechanisms by which a processor may execute instructions. In the example of FIG. 15, execution entities 1565 may include ALU/Multiplication Units (MUL) 1566, ALUs 1567, and Floating Point Units (FPU) 1568. In one embodiment, such entities may make use of information contained within a given address 1569. Execution entities 1565 in combination with stages 1530, 1550, 1555, 1560, 1570 may collectively form an execution unit.

Unit 1510 may be implemented in any suitable manner. In one embodiment, unit 1510 may perform cache control. In such an embodiment, unit 1510 may thus include a cache 1525. Cache 1525 may be implemented, in a further embodiment, as an L2 unified cache with any suitable size, such as zero, 128 k, 256 k, 512 k, 1M, or 2M bytes of memory. In another, further embodiment, cache 1525 may be implemented in error-correcting code memory. In another embodiment, unit 1510 may perform bus interfacing to other portions of a processor or electronic device. In such an embodiment, unit 1510 may thus include a bus interface unit 1520 for communicating over an interconnect, intraprocessor bus, interprocessor bus, or other communication bus, port, or line. Bus interface unit 1520 may provide interfacing in order to perform, for example, generation of the memory and input/output addresses for the transfer of data between execution entities 1565 and the portions of a system external to instruction architecture 1500.

To further facilitate its functions, bus interface unit 1520 may include an interrupt control and distribution unit 1511 for generating interrupts and other communications to other portions of a processor or electronic device. In one embodiment, bus interface unit 1520 may include a snoop control unit 1512 that handles cache access and coherency for multiple processing cores. In a further embodiment, to provide such functionality, snoop control unit 1512 may include a cache-to-cache transfer unit that handles information exchanges between different caches. In another, further embodiment, snoop control unit 1512 may include one or more snoop filters 1514 that monitors the coherency of other caches (not shown) so that a cache controller, such as unit 1510, does not have to perform such monitoring directly. Unit 1510 may include any suitable number of timers 1515 for synchronizing the actions of instruction architecture 1500. Also, unit 1510 may include an AC port 1516.

Memory system 1540 may include any suitable number and kind of mechanisms for storing information for the processing needs of instruction architecture 1500. In one embodiment, memory system 1504 may include a load store unit 1530 for storing information such as buffers written to or read back from memory or registers. In another embodiment, memory system 1504 may include a translation lookaside buffer (TLB) 1545 that provides look-up of address values between physical and virtual addresses. In yet another embodiment, bus interface unit 1520 may include a Memory Management Unit (MMU) 1544 for facilitating access to virtual memory. In still yet another embodiment, memory system 1504 may include a prefetcher 1543 for requesting instructions from memory before such instructions are actually needed to be executed, in order to reduce latency.

The operation of instruction architecture 1500 to execute an instruction may be performed through different stages. For example, using unit 1510 instruction prefetch stage 1530 may access an instruction through prefetcher 1543. Instructions retrieved may be stored in instruction cache 1532. Prefetch stage 1530 may enable an option 1531 for fast-loop mode, wherein a series of instructions forming a loop that is small enough to fit within a given cache are executed. In one embodiment, such an execution may be performed without needing to access additional instructions from, for example, instruction cache 1532. Determination of what instructions to prefetch may be made by, for example, branch prediction unit 1535, which may access indications of execution in global history 1536, indications of target addresses 1537, or contents of a return stack 1538 to determine which of branches 1557 of code will be executed next. Such branches may be possibly prefetched as a result. Branches 1557 may be produced through other stages of operation as described below. Instruction prefetch stage 1530 may provide instructions as well as any predictions about future instructions to dual instruction decode stage.

Dual instruction decode stage 1550 may translate a received instruction into microcode-based instructions that may be executed. Dual instruction decode stage 1550 may simultaneously decode two instructions per clock cycle. Furthermore, dual instruction decode stage 1550 may pass its results to register rename stage 1555. In addition, dual instruction decode stage 1550 may determine any resulting branches from its decoding and eventual execution of the microcode. Such results may be input into branches 1557.

Register rename stage 1555 may translate references to virtual registers or other resources into references to physical registers or resources. Register rename stage 1555 may include indications of such mapping in a register pool 1556. Register rename stage 1555 may alter the instructions as received and send the result to issue stage 1560.

Issue stage 1560 may issue or dispatch commands to execution entities 1565. Such issuance may be performed in an out-of-order fashion. In one embodiment, multiple instructions may be held at issue stage 1560 before being executed. Issue stage 1560 may include an instruction queue 1561 for holding such multiple commands. Instructions may be issued by issue stage 1560 to a particular processing entity 1565 based upon any acceptable criteria, such as availability or suitability of resources for execution of a given instruction. In one embodiment, issue stage 1560 may reorder the instructions within instruction queue 1561 such that the first instructions received might not be the first instructions executed. Based upon the ordering of instruction queue 1561, additional branching information may be provided to branches 1557. Issue stage 1560 may pass instructions to executing entities 1565 for execution.

Upon execution, writeback stage 1570 may write data into registers, queues, or other structures of instruction set architecture 1500 to communicate the completion of a given command. Depending upon the order of instructions arranged in issue stage 1560, the operation of writeback stage 1570 may enable additional instructions to be executed. Performance of instruction set architecture 1500 may be monitored or debugged by trace unit 1575.

FIG. 16 is a block diagram of an execution pipeline 1600 for an instruction set architecture of a processor, in accordance with embodiments of the present disclosure. Execution pipeline 1600 may illustrate operation of, for example, instruction architecture 1500 of FIG. 15.

Execution pipeline 1600 may include any suitable combination of steps or operations. In 1605, predictions of the branch that is to be executed next may be made. In one embodiment, such predictions may be based upon previous executions of instructions and the results thereof. In 1610, instructions corresponding to the predicted branch of execution may be loaded into an instruction cache. In 1615, one or more such instructions in the instruction cache may be fetched for execution. In 1620, the instructions that have been fetched may be decoded into microcode or more specific machine language. In one embodiment, multiple instructions may be simultaneously decoded. In 1625, references to registers or other resources within the decoded instructions may be reassigned. For example, references to virtual registers may be replaced with references to corresponding physical registers. In 1630, the instructions may be dispatched to queues for execution. In 1640, the instructions may be executed. Such execution may be performed in any suitable manner. In 1650, the instructions may be issued to a suitable execution entity. The manner in which the instruction is executed may depend upon the specific entity executing the instruction. For example, at 1655, an ALU may perform arithmetic functions. The ALU may utilize a single clock cycle for its operation, as well as two shifters. In one embodiment, two ALUs may be employed, and thus two instructions may be executed at 1655. At 1660, a determination of a resulting branch may be made. A program counter may be used to designate the destination to which the branch will be made. 1660 may be executed within a single clock cycle. At 1665, floating point arithmetic may be performed by one or more FPUs. The floating point operation may require multiple clock cycles to execute, such as two to ten cycles. At 1670, multiplication and division operations may be performed. Such operations may be performed in four clock cycles. At 1675, loading and storing operations to registers or other portions of pipeline 1600 may be performed. The operations may include loading and storing addresses. Such operations may be performed in four clock cycles. At 1680, write-back operations may be performed as required by the resulting operations of 1655-1675.

FIG. 17 is a block diagram of an electronic device 1700 for utilizing a processor 1710, in accordance with embodiments of the present disclosure. Electronic device 1700 may include, for example, a notebook, an ultrabook, a computer, a tower server, a rack server, a blade server, a laptop, a desktop, a tablet, a mobile device, a phone, an embedded computer, or any other suitable electronic device.

Electronic device 1700 may include processor 1710 communicatively coupled to any suitable number or kind of components, peripherals, modules, or devices. Such coupling may be accomplished by any suitable kind of bus or interface, such as I²C bus, System Management Bus (SMBus), Low Pin Count (LPC) bus, SPI, High Definition Audio (HDA) bus, Serial Advance Technology Attachment (SATA) bus, USB bus (versions 1, 2, 3), or Universal Asynchronous Receiver/Transmitter (UART) bus.

Such components may include, for example, a display 1724, a touch screen 1725, a touch pad 1730, a Near Field Communications (NFC) unit 1745, a sensor hub 1740, a thermal sensor 1746, an Express Chipset (EC) 1735, a Trusted Platform Module (TPM) 1738, BIOS/firmware/flash memory 1722, a DSP 1760, a drive 1720 such as a Solid State Disk (SSD) or a Hard Disk Drive (HDD), a wireless local area network (WLAN) unit 1750, a Bluetooth unit 1752, a Wireless Wide Area Network (WWAN) unit 1756, a Global Positioning System (GPS), a camera 1754 such as a USB 3.0 camera, or a Low Power Double Data Rate (LPDDR) memory unit 1715 implemented in, for example, the LPDDR3 standard. These components may each be implemented in any suitable manner.

Furthermore, in various embodiments other components may be communicatively coupled to processor 1710 through the components discussed above. For example, an accelerometer 1741, Ambient Light Sensor (ALS) 1742, compass 1743, and gyroscope 1744 may be communicatively coupled to sensor hub 1740. A thermal sensor 1739, fan 1737, keyboard 1746, and touch pad 1730 may be communicatively coupled to EC 1735. Speaker 1763, headphones 1764, and a microphone 1765 may be communicatively coupled to an audio unit 1764, which may in turn be communicatively coupled to DSP 1760. Audio unit 1764 may include, for example, an audio codec and a class D amplifier. A SIM card 1757 may be communicatively coupled to WWAN unit 1756. Components such as WLAN unit 1750 and Bluetooth unit 1752, as well as WWAN unit 1756 may be implemented in a Next Generation Form Factor (NGFF).

FIG. 18 is a block diagram of a system 1800 for implementing logic and an instruction for interrupt and exception tracing, handling, and reporting, according to embodiments of the present disclosure. In one embodiment, these may include performance monitoring capabilities to identify and output control flow information in association with, for example, interrupts, exceptions, virtual machine entries, virtual machine exits, or other events. The control flow information may include control flow event information generated by processor trace hardware on a processor, such as processor 1806. In another embodiment, these may include indications of how interrupt masking has been employed in system 1800.

System performance, power, and responsiveness can directly be impacted by many events on system 1800 including interrupts, faults, exceptions and Virtual Machine transitions generated while executing instructions. All of these cases might impact the flow of execution on processor 1806, impacting software functionality, performance, power, stability and reliability. These may be generated by in-order or out-of-order processing cores, such as those that include execution units 1822, or by intellectual property (IP) cores or units, such as IP cores 1830. SoC designs tend to have many special purpose IP units integrated onto the same die as the general purpose cores or CPU. These IP units may be accessed via device drivers running on the general purpose cores or CPU. An IP unit may obtain the central processor's attention for handling through interrupts. Because of this, system 1800 may encounter more interrupts according to how many unique IP cores 1830 resident on system 1800, which may increase if system 1800 is a SoC. In one embodiment, system 1800 may track interrupts precisely and with low overhead in order to achieve a balance between power and performance.

System 1800 may track interrupts, masking, exceptions, and faults in order to provide better performance as well operating with stable debugging and good reliability. System 1800 may experience many unnecessary page fault exceptions from software running on processor 1806. Furthermore, system 1800 may utilize virtualization. When multiple guest operating systems are present on system 1800, profiling using software instrumentation may become difficult. Visibility into these events in an operating-system agnostic manner alleviates this problem.

Furthermore, as the number of interrupts that system 1800 may handle increases, system 1800 may need better visibility into when and how interrupts are masked. While interrupts are masked, they might not be handled while the time critical code executes. Masking may be performed for a variety of reasons. A software entity such as an operating system or device driver might mask interrupts prior to executing a section of code that is time critical. For example, a device driver might mask interrupts while it offloads data from an IP core 1830. An operating system may mask interrupts while holding locks on critical resources, or during context switches. If interrupts were not masked, the arrival of an interrupt during these sections of code might result in a delay in the execution of that code while an interrupt handler 1828 executes.

While code executing with its interrupts masked is more deterministic, the performance system 1800 may suffer in such a mode if interrupts are masked for too long. Some performance and functional failures may be attributed to interrupt masking when servicing of time-critical interrupts is delayed. Accordingly, system 1800 may include facilities for determining when interrupts are masked, as well as which agents in the system are masking interrupts. Software must otherwise attempt to infer whether interrupts are masked based on the absence of interrupts during a certain time window. However, such inferences are not reliable nor can they be matched against other processor trace information. Thus, it is not possible with software to determine which software is masking interrupts, nor can exactly when interrupts are masked. Also, when profiling execution itself uses interrupts such as PMI interrupts to collect data, interrupt masking will introduce significant error into profiling data. In one embodiment, system 1800 may determine tracing information on when interrupts are masked, unmasked and the memory locations and reasons for masking. In another embodiment, profiling of execution may be paused when or marked when interrupts are determined to be masked.

In one embodiment, the tracking of interrupts and other messages on system 1800 may include determining the code that generated the interrupt. In another embodiment, such tracking may include determining whether interrupt masking has been enabled or disabled. In still yet another embodiment, the tracking may include tracking of virtualization messages.

In one embodiment, system 1800 may include a processor trace unit (PTU) 1826 to expose the path of code execution on processor 1806. In another embodiment, PTU 1826 may illustrate why certain code paths were taken. PTU 1826 may include logic to perform the functionality described herein, wherein PTU 1826 may produce metadata about certain types of control flow events. This metadata may be used by users of system 1800 to better understand the behavior of processor 1806 as it executes their code. This may improve or facilitate debugging.

Control flow events that may be identified and traced by PTU 1826 may include, for example, asynchronous events such as interrupts, exceptions, or faults. Furthermore, such control flow events may include returns from a software handler, such as an interrupt handler, fault handler, or VM machine, in response to such asynchronous events. Examples of these may include IRET or VMentry messages or interrupts. These control flow events might not be foreseeable during execution of code, which is why they may require handling with an interrupt handler or other software entity outside of the normal execution of an application's source assembly code.

In order to provide such metadata, system 1800 may include any suitable number and kind of components. Although some elements of system 1800 are described as performing certain functionality, any suitable portion of system 1800 may perform such functionality as it is able.

System 1800 may include any suitable number and kind of elements to enhance interrupt and similar message tracing. In one embodiment, system 1800 may include an indicator that information about interrupts and similar messages will be tracked and reported. Such an indicator may include a register or bit within a register. System 1800 may accept and execute instructions to set or clear this indicator. When enabled, PTU 1826 may perform the reporting described herein for events such as interrupts. The bit may be called, for example, Event Tracing Enable Bit 1842. The bit may reside, for example, in a control register such as IA32_RTIT 1840. This control register may include other bits for enabling various operations of PTU 1826, which may be used in conjunction with Event Tracing Enable Bit 1842 to enable the reporting of information by PTU 1826 described herein. In a further embodiment, Event Tracing Enable Bit 1842 may also be used to determine whether or not interrupt masking has been enabled. System 1800 may execute instructions enabling or disabling event tracing, interrupt handling, and other operations as described in the present disclosure. Such enabling or disabling may be made by setting or clearing enablement structures such as bits within IA32RIT_CTL 1840.

In another embodiment, system 1800 may include logic to generate Control Flow Event (CFE) packets 1832 in association with interrupts or other messages. These may be generated by PTU 1826. In a further embodiment, CFE packets 1832 may indicate a change in control flow due to many different cases including interrupts, exceptions and entries/exits from a Virtual Machine. The CFE packet 1832 may be generated when a control flow event is taken, and may provide the type of event (interrupts, exceptions, faults, NMI, etc.). Control flow events may be asynchronous (e.g. interrupts) or synchronous (e.g. IRET, VMEntry).

In yet another embodiment, system 1800 may include logic to generate Event Data (EVD) packets 1834 in association with interrupts or other messages. These may be generated by PTU 1826. In a further embodiment, a given EVD packet 1834 will always bind to a CFE packet 1832. However, in some embodiments a CFE packet 1832 might not need an associated EVD packet 1834. In another, further embodiment, an EVD packet 1834 will precede an associated CFE packet 1832. For example, one or more EVD packets 1834 may bind to the next CFE 1832 packet that is generated. EVD packet 1834 may include additional metadata about the control flow event that caused generation of CFE packet 1832.

PTU 1826 may generate other information about control flow events, not shown in FIG. 18. For example, PTU 1826 may generate information about instruction pointers or whether full instruction trace is enabled or not. PUT 1826 may generate such information through, for example, follow-up (FUP) packets, target instruction pointer (TIP) packets, or mode.exec packets.

Other mechanisms of tracking interrupt patterns may be problematic. For example, interrupt patterns of other processor traces may be difficult to extract from trace dump information as the metadata such as type of interrupt, interrupt vector and may be embedded in a large amount of data. Operating-system-based logging tools might not be available, particularly for SoC or embedded systems. Furthermore, these cannot provide visibility into all events, such as System Management Interrupts. Also, aligning operating system logs of event information with processor trace logs of control flow information is imprecise due to the lack of precise time-stamping of all data. Software logging incurs significant overhead, may not be reliable, and is not always available. System 1800 also provides an effective way to track the relationship between power management and interrupts, which can have significant impact on software functionality and responsiveness. By correlating generated events with hardware events within hardware in processor 1806, significant visibility may be gained.

System 1800 may include any suitable number and kind of elements for determining and reporting whether interrupt masking is enabled. In one embodiment, system 1800 may include a control field to enable or disable tracking of interrupt masking. Enabling such tracking may include reporting with messages or packets about the status of interrupt masking. The messages may include new types of messages or information may be included on existing kinds of messages. In a further embodiment, system 1800 may use event tracing enable bit 1842 to enable reporting of whether interrupt masking is activated. Enabling such reporting may be in addition to enabling of CFE packets 1832 and EVD packets 1834.

In another embodiment, system 1800 may provide information when the interrupt masking is activated or deactivated. System 1800 may provide such information by, for example, generating packets or messages to be sent when the interrupt masking is activated or deactivated. For example, the packets may be generated when the value of an interrupt flag in registers is changed. Such a flag may include, for example, an interrupt flag 1840 within an EFLAGS register 1836. The flag may also be within another suitable register depending upon processor implementation, such as a RFLAGs register.

The packets or messages may further indicate the present value of the interrupt flag after the value has been altered or changed. In a further embodiment, the present value of the interrupt flag may be indicated in IF payload bit 1846. This bit or other information used to represent the status or change in status of interrupt masking may be set in any suitable location, and may be included in any suitable message or packet. In a further embodiment, system 1800 may use mode.exec packets 1844 to carry IF payload bit 1846. Mode.exec packets might be otherwise generated when, for example, an execution mode has changed. Such a mode may include, for example, going between privileged kernel and unprivileged user modes. In such embodiments, mode.exec packets 1844 carrying an updated IF payload bit 1846 are sent only if the interrupt flag controlling masking is changed.

In yet another embodiment, a packet generated to report the status of interrupt masking may be bound to the source of changing the interrupt masking. For example, the mode.exec packet 1844 may include payloads or other fields to identify the instruction pointer to determine where the interrupt masking was changed. Such instruction pointer tracing may be provided by, for example, PTU 1826.

In still yet another embodiment, a packet generated to report the status of interrupt masking may be bound to a time to determine when interrupts are masked and unmasked. Such a time may be provided by, for example, PTU 1826 and may be based upon a hardware clock of processor 1806.

Accordingly, system 1800 may efficiently determine when interrupt masking is enabled or disabled, as well as determine the source and time of such action. System 1800 might not need to rely upon inferences for such information. Packets that are returned may be used for debugging, wherein users of system 1800 may accurately trace the execution of instructions to determine the source and time of interrupt masking enabling or disabling. Furthermore, system 1800 may thus yield information about how long interrupts are masked for a give core or cores.

Processor 1806 may be implemented in any suitable manner, including in part by elements as described in FIGS. 1-17. Execution of instructions 1828 may be performed by embodiments of a processor pipeline. Processor 1806 may include multiple cores, engines, and out-of-order processing. Processor 1806 may include a front end 1808 to receive or fetch instructions from memory including an instruction stream. Front end 1808 may include a fetcher 1810 to efficiently fill the pipeline with possible instructions to execute. Front end 1808 may include a decoder 1812 to decode an instruction to opcodes for execution, determine its meaning, obtain side effects, data required, data consumed, and data to be produced. A binary translator may be used to optimize code. Instructions may be resident in an instruction stream or memory subsystem as produced by, for example a compiler, interpreter, or binary translator. The information may be passed to an out-of-order or in-order execution engine in an execution pipeline 1816. Execution pipeline 1816 may include a rename and allocate unit 1818 for renaming instructions for out-of-order execution, storing such renaming conventions in a reorder buffer (ROB) coextensive with a retirement unit 1824 so that instructions can appear to be retired in the order that they were received. Rename and allocate unit 1818 may further allocate resources for execution of instructions in parallel. The scheduler 1820 may schedule instructions to execute on execution units 1822 when inputs are available. Outputs of execution units 1822 may queue in the ROB. Front end 1808 may attempt to anticipate any behaviors that will prevent instructions from executing in a sequential stream and may fetch streams of instructions that might execute. When there is, for example, a misprediction, the ROB may inform the front-end and a different set of instructions might be executed instead. Front end 1808 may store data such as metadata for branch prediction. Execution may be passed from front end 1808 or execution pipeline 1816 to specific ones of IP cores 1830 for execution. In some embodiments, processor 1806 may significantly utilize IP cores 1830, particularly in SoC designs.

In operation, system 1800 may process and execute instructions. These instructions may cause generation of interrupts, faults, or other messages that are to be traced as described within the present disclosure. Furthermore, these instructions may enable, disable, or otherwise carry out the tracing of interrupt and similar messages as described within the present disclosure. Interrupts, faults, and similar messages may be generated by a main CPU core, such as one including execution pipeline 1816 or execution units 1822, or by any one of other logic cores on processor 1806 such as IP cores 1830. Interrupts and faults may be handled by, for example, a fault/interrupt handler 1828. Although a single handler is illustrated, system 1800 may include any suitable number and kind of handlers. Upon detection of traced execution or of changes to interrupt masking, PTU 1826 may generate suitable messages as described above.

FIG. 19 is a more detailed illustration of elements of system 1800, according to embodiments of the present disclosure.

A more detailed illustration of an example embodiment of CFE packet 1832 is shown, although any suitable structure and format may be used. CFE packet 1832 may include one or more bits to identify that it is a CFE packet. In one embodiment, CFE packet 1832 may include a field to specify the type or sub-type of CFE packet that it constitutes. This may match the kind of event that generated CFE packet 1832. In another embodiment, CFE packet 1832 may include a field to hold vector data, if needed, to store various data that may be used in evaluating the nature of the event that generated CFE packet 1832. Such data may specify, for example, INTR or exception information. The field for vector data may be otherwise reserved for types of CFE packets not using the vector. In a further embodiment, CFE packet 1832 may be bound to one or more EVD packets 1834 to provide yet additional information about the event that generated CFE packet 1832. In yet another embodiment, CFE packet 1832 may include an identifier of whether the CFE packet is followed by a FUP, or flow update packet. This identifier may be indicated by “IP” because the FUP may include an indicator of an instruction pointer related to the use of the event generating the CFE packet. CFE packet 1832 may also include fields to identify a source of the generated event.

A CFE packet 1832 may be sent upon various events. Chart 2002 illustrates possible values and variations of CFE packet 1832, indexed by the type or subtype of CFE that may be specified in a field of a given CFE packet 1832. These types of CFE may correspond to the events that can generate a CFE packet.

For example, a CFE packet may be of an INTR type, wherein the interrupt was generated based upon a received input over a signal line. The INTR type may be used for interrupts, exceptions, faults, non-maskable interrupts, INT n, or other events not otherwise falling within another category. INTR type may include a vector with an identifier of such INTR message. An INTR type may be associated with a FUP messages, and the type of FUP message may depend upon the precise event that was generated. The FUP may include an address of an instruction that has not yet completed.

A CFE packet may be of an IRET type, wherein the interrupt is of an interrupt return type. The vector may be reserved, the FUP field may be set and such a message may include the instruction pointer of the calling function (CLIP), to where execution should be returned.

A CFE packet may be of an SMI type, wherein the interrupt is of a system management interrupt type. The vector may be reserved, the FUP field may be set and such a message may include the next linear instruction pointer (NLIP).

A CFE packet may be of an RSM type, wherein the event is resuming from system management. The vector may be reserved, the FUP field might not be used.

A CFE packet may be of an SIPI type, wherein the interrupt is of a startup inter-processor interrupt type. The vector may be used and the FUP filed may be set and such a message may include the NLIP.

A CFE packet may be of an INIT type, wherein the interrupt is of an initialization interrupt type. The vector may be reserved, the FUP field might indicate that a FUP message with the NLIP will be sent.

A CFE packet may be of a VMEntry type, wherein the event was generated by entry by a virtual machine. In such a case, the FUP field may be set and the FUP message may include an instruction pointer of calls to, for example, VMLAUNCH or VMRESUME.

A CFE packet may be of a VMEXIT type, wherein the event was generated by exit from a virtual machine. In such a case, the FUP message may depend on the type of exit and will be consistent with a guest IP saved in a VM control structure.

A CFE packet may be of a VMEXIT_VEC type, wherein the event was generated by a VMEXIT that in turn was caused by an INTR event. Such an event may have included an INTR event as shown above.

A SHUTDOWN packet may be of a shutdown message type, wherein system 1800 is attempting to shut down and appropriate measures are to be taken in response.

EVD packets 1834 may include metadata for debugging the control flow changes that are reported in associated CFE packets 1832. An EVD packet 1834 may be sent when additional data is available for supplementing the associated CFE packet 1832. In one embodiment, an EVD packet 1834 may be bound to the next following CFE packet 1832. In another embodiment, an EVD packet is never issued as a standalone packet, requiring that it is always followed by, and will bind to, a CFE packet 1832. There may be multiple EVD packets that precede a single CFE packet. This is expected for VMExit cases, where VM exit qualification and VM exit reason packets will be generated prior to a CFE VMExit packet.

A more detailed illustration of an example embodiment of EVD packet 1834 is shown, although any suitable structure and format may be used. EVD packet 1834 may include one or more bits to identify that it is an EVD packet 1834. In one embodiment, EVD packet 1834 may include a field to specify the type or sub-type of EVD packet that it constitutes. This may identify the kind of contents that it includes, such as those in a payload. In another embodiment, EVD packet 1834 may include a field to specify the actual contents of the payload. The type of EVD packet might not necessarily match, one-for-one, with a type of CFE packet, as a given type of EVD packet might be used with multiple kinds of CFE packets. Moreover, multiple, different types of EVD packets may be sent for a single CFE packet. For example,

Example types and payloads of EVD packet 1834 are illustrated in chart 2004, although any suitable type of EVD packet 1834 may be used. EVD packet 1834 may be of a type associated with page faults. EVD packet 1834, in such a case, may specify the linear address of the page fault within the associated payload field.

EVD packet 1834 may be of a type of VM Exit Reason. EVD packet 1834, in such a case, may specify a thirty-two bit field of information about the cause of a VM problem. This information may be stored within the payload field. The information may designate, for example, whether the error was encountered on a VM exit or entry, whether virtual machine root information, or whether the VM exit was caused for a non-error related purpose.

EVD packet 1834 may be of a type of VM Exit Qualification. EVD packet 1834, in such a case, may specify a sixty-four bit field of information about the cause of the VM exit due to debug exceptions, page-fault exceptions, start-up IPIs, task switches; invalid pages, VM-specific problems, control-register accesses, etc. This information may be stored within the payload field. This kind of packet may further supplement information from a VM Exit Reason packet.

A more detailed illustration of an example embodiment of an IA32_RTIT register 1840 is shown, although any suitable structure and format may be used. Although a single register 1840 is shown, the functionality described herein may be implemented by any suitable number and combination of registers. For example, bits that may be set or cleared by user software may be implemented by a control register, while read-only bits that indicate the status of the system and are set or cleared by the processor may be implemented by a status register.

In one embodiment, IA32_RTIT register 1840 may include a bit 1842 for indicating whether event tracing as described within the present disclosure will be performed. IA32_RTIT register 1840 may include other settings related to performance monitoring. In other embodiments, such settings might be located within other registers or locations.

For example, IA32_RTIT register 1840 may include fields to specify whether hardware-based processor tracing is even enabled in system 1800. This may include a bit for Trace Enabling (TraceEn). Setting or clearing this field may enable or disable such tracing. In some cases, software may set or clear this field. This may enable, for example, PTU 1826.

IA32_RTIT register 1840 may include fields to specify whether tracing packets will be generated for a variety of events in system 1800. Such events may include branch operations. These fields may include a bit for Branch Enabling (BranchEn). Setting or clearing this field may enable or disable such change-of-flow instruction tracing, wherein branch operations are tracked. In some cases, software may set or clear this field. When this field is set, packets such as FUP (follow up packets), TIP (target IP) packets, TIP.PGE (packet generation enable) packets, TIP.PGD (packet generation disable) packets, TNT (taken/not taken) packets, or MODE packets (such as MODE.Exec, and MODE.TSX packets) may be generated.

IA32_RTIT register 1840 may include fields to indicate whether tracing is enabled in system 1800 and that trace packet generation is active. This may include a bit for Trigger Enabling (TriggerEn). Setting or clearing this field may be restricted to internal use only, and software might only be able to read such a bit. Thus, it may indicate whether tracing has been successfully enabled.

IA32_RTIT register 1840 may include fields to indicate whether tracing is enabled in system 1800 for the current context. The field may indicate whether the processor is in the state or mode that software configured hardware to trace. This may include a bit for Context Enabling (ContextEn). Setting or clearing this field may be restricted to internal use only, and software might only be able to read such a bit. Thus, it may indicate whether tracing has been successfully enabled for the present context of thread execution.

IA32_RTIT register 1840 may include fields to indicate whether tracing is enabled in system 1800 for the current instruction pointer. It may show whether the instruction pointer is within the range of instruction pointers that the trace unit is configured to watch. This may include a bit for Filter Enable (FilterEn). Setting or clearing this field may be restricted to internal use only, and software might only be able to read such a bit. Thus, it may indicate whether tracing has been successfully enabled for the present instruction pointer.

A more detailed illustration of an example embodiment of a packet to report changes to interrupt masking is shown, although any suitable structure and format may be used. For example, a mode.exec packet 1844 may be used to report IF payload bit 1846. IF payload bit 1846 may indicate the value of the interrupt flag as set or changed by software. The interrupt flag may include, for example, interrupt flag 1840 in an appropriate register, such as the EFLAGS or RFLAGS register. IF payload bit 1846 may be included as bit 2 in a mode.exec packet 1844 payload or information field. In a further embodiment, IF payload bit 1846 may be set to the logical AND operation of interrupt flag 1840 and Event Tracing Enable Bit 1842.

FIG. 20 is an illustration of example operation of system 1800 to perform event tracing, according to embodiments of the present disclosure. FIG. 20 may illustrate operation of event tracing given the example event of a page fault.

At a certain point in time, a user process, such as Process1 (P1) may be executed on system 1800. At a later point in time, a page fault may be encountered.

In response to the page fault, branch trace packets may be issued. Such branch trace packets may be generated by PTU 1826 when such branch execution tracing is suitable enabled on system 1800. The branch trace packets may include, for example, an FUP packet identifying P1 and the instruction pointer, as well as a target IP packet identifying a page. The FUP may identify the current instruction pointer and the TIP may identify the target instruction pointer of the branched operation arising from the page fault.

In one embodiment, in response to the page fault, event trace packets may be issued if event tracing is enabled by, for example, event tracing enable bit 1842. The event trace packets may include an EVD packet 1834 identified as a page fault linear address packet according to its type field. The actual address causing the page fault may be stored in the payload of the EVD packet 1834 that is generated. Thus, EVD.PFA may include the addresses that caused the page fault. The EVD packet 1834 may be followed by a corresponding CFE packet 1832. The CFE packet 1832 may be of type INTR according to its type field. The vector of the CFE packet 1832 may include data showing that it was a page fault that caused the interrupt or fault.

After the page fault interrupt, a kernel or interrupt serve routine may handle the page fault. When the page fault has been handled, an IRET interrupt may be issued to note that the execution may resume.

In response to the IRET, branch trace packets may be issued. Such branch trace packets may be generated by PTU 1826 when such branch execution tracing is suitable enabled on system 1800. The branch trace packets may include, for example, a target IP packet identifying the original page so that P1 can continue executing.

In another embodiment, in response to the IRET, event trace packets may be issued as long as when event tracing is enabled by, for example, event tracing enable bit 1842. The event trace packets may include a CFE packet 1832 with a type identifier for IRET events.

Branch trace packets, by themselves, might only indicate the branch information associated with the page fault and subsequent recovery. There would be no indication regarding the reason for the branch. The event trace packets may provide information sufficient to illustrate the cause of the branch recorded in the branch trace packets. Furthermore, the EVD packets 1834 may provide the information about exactly which instruction or access caused the page fault. As the event trace packets include such information and are bound at an instruction level, the events may be precisely tracked and evaluated.

FIG. 21 is an illustration of example operation of system 1800 to perform interrupt mask tracing, according to embodiments of the present disclosure

Interrupt mask tracing information may be generated upon any suitable conditions in which interrupt masking will change. In one embodiment, such conditions may include an attempted change to interrupt flag 1840. A mode.exec packet 1844 may be issued. Interrupt mask tracing information may be populated in any suitable manner. IF payload bit 1846 may be populated within an appropriate packet, such as mode.exec packet 1844. IF payload bit 1846 may be populated with the value of the changed interrupt flag 1840. In another embodiment, IF payload bit 1846 may be populated with the logical AND of the value of the changed interrupt flag 1840 and Event Tracing Enable Bit 1842. Thus, if event tracing is not enabled, a mode.exec packet 1844 that is generated for other reasons (beyond the scope of this disclosure), then the recipient will act as-if interrupt masking is turned off.

In one embodiment, system 1800 may employ packet compression to reduce the number of mode.exec packets that are sent out in order to track changes to interrupt masking. For example, if software is executing code that is not being traced by PTU 1826, according to, for example, filtering options reflecting in bits of IA32_RTIT register 1840, then changes to the interrupt flag will not immediately generate a mode.exec packet. However, when the software enters code that is being traced, if the value of the interrupt flag has changed since the last mode.exec packet was sent, a new mode.exec patent might be generated with the new interrupt flag value.

Thus, in some embodiments, interrupt mask tracing information may be generated upon other conditions in which interrupt masking will change. For example, interrupt mask tracking information, such as the setting of IF payload bit 1846, may be populated when there are attempted changes to IF 1840 and event tracing enable bit 1842 is set. In another example, interrupt mask tracking information may be populated when the triggering enable bit is also set. In yet another example, interrupt mask tracking information may be populated when the context enable bit is also set. In still another example, interrupt mask tracking information may be populated when the filter enable bit is also set. These bits may be included in, for example, IA32_RTIT register 1840 with the event tracing enable bit. These additional conditions may restrict interrupt mask tracing to situations in which such tracing is actually possible with respect to other settings of system 1800. A mode.exec packet 1844 may be issued.

In yet another embodiment, interrupt mask tracing information may be generated upon other conditions in which interrupt masking might change as a side effect. For example, if the logical combination of the enabling bits (i.e., a combination of whatever bits are used among event enabling, trigger enabling, context enabling, and filter enabling) become set, when previously not all such bits were set, and if interrupt flag 1840 is different from a last-issued mode.exec packet 1844, then interrupt mask tracing information may be generated and a mode.exec packet 1844 issued. This case may represent cases where a change was made to IF 1840, but tracking was not enabled. Thus, when tracking is later enabled, and a change was made to IF 1840 in the meantime since the last mode.exec packet 1844 was sent, a new mode.exec packet 1844 reflecting the new value of IF 1840 should be generated. If processor tracing in general is disabled, then a mode.exec packet may be sent later. A new value of IF 1840 can be generated for such a mode.exec packet.

Issuance of a mode.exec packet 1844 may be followed by issuance of a FUP or TIP packet that provide the instruction pointer at which the new interrupt flag value applies. TIPs may be used when the interrupt flag is modified as part of a control flow transfer operations, while FUPs may be used when there is no control flow change. In one embodiment, the TIP or FUP following mode.exec packet 1844 may be used to bind the change of the interrupt flag value to a particular address.

FIG. 22 is flow chart of a method 22000 for interrupt and exception handling, according to embodiments of the present disclosure. Method 2200 may be initiated by any suitable criteria. Furthermore, although method 2200 describes operation of particular elements, method 2200 may be performed by any suitable combination or type of elements. For example, method 2200 may be implemented by the elements illustrated in FIGS. 1-21 or any other system operable to implement method 2000. As such, the preferred initialization point for method 2200 and the order of the elements comprising Method 2000 may depend on the implementation chosen. In some embodiments, some elements may be optionally omitted, reorganized, repeated, or combined. Moreover, portions of method 2200 may be executed in parallel within itself or with portions of method 2300.

At 2205, in one embodiment event tracing may be enabled. Such event tracing may be enabled through setting of appropriate register values. Furthermore, the event tracing may be enabled in conjunction with other processor tracing, such as branch operation tracing.

At 2210, instructions to be executed may be fetched. At 2215, the instructions may be decoded and at 2220 they may be executed.

At 2225, in or after any of 2210-2220, in one embodiment it may be determined that an interrupt, fault, exception or other message has occurred. The message may have been generated in association with execution of a given instruction at a spot within code corresponding to an instruction pointer value.

At 2230, it may be determined that event tracing was enabled. Otherwise, method 2200 may proceed to 2255. At 2235, based upon event tracing being enabled and upon the interrupt, in one embodiment a CFE packet may be created. The CFE packet may identify the type of interrupt or other message. In another embodiment, at 2240 one or more EVD packets may be created. The EVD packet may include additional information about the interrupt or other message. In yet another embodiment, at 2245, one or more FUP packets may be generated. The FUP packets may identify an instruction pointer of the code causing the interrupt.

At 2250, in one embodiment, the packets may be sent to a trace subscriber. The EVD packet or packets might be sent first, followed by the CFE packet, followed by the FUP packet or packets. Additionally, branch execution tracing packets may be sent.

At 2255, it may be determined whether method 2200 will repeat at, for example 2205 or 2210, or terminate. Method 2200 may optionally repeat in any suitable manner.

FIG. 23 is flow chart of another method 2300 for tracking interrupt masking, according to embodiments of the present disclosure. Method 2300 may be initiated by any suitable criteria. Furthermore, although Method 2300 describes operation of particular elements, method 2300 may be performed by any suitable combination or type of elements. For example, method 2300 may be implemented by the elements illustrated in FIGS. 1-21 or any other system operable to implement method 2300. As such, the preferred initialization point for method 2300 and the order of the elements comprising method 2300 may depend on the implementation chosen. In some embodiments, some elements may be optionally omitted, reorganized, repeated, or combined. Moreover, portions of method 2300 may be executed in parallel within itself or with portions of method 2200.

At 2305, event tracing parameters may be enabled or disabled. In one embodiment, such event tracing parameters may include a bit in a register to enable tracking of interrupt masking. Furthermore, execution tracing may be enabled or disabled as well as other parameters of execution tracing.

At 2310, in one embodiment it may be determined whether an attempt has been made to change an IF. If not, method 2300 may proceed to 2325. Otherwise, method 2300 may proceed to 2315.

At 2315, in one embodiment it may be determined whether event tracing has been enabled. If not, method 2300 may proceed to 2325. Otherwise, method 2300 may proceed to 2320.

At 2320, it may be determined whether supporting tracing parameters, such as trigger, context, or filter enable bits have been set. If so, method 2300 may proceed to 2345 to generate a reporting packet. Otherwise, method 2300 may proceed to 2325 to determine if other reasons exist for generating a reporting packet.

At 2325, in one embodiment it may be determined whether a reporting packet has been created and will issue for other reasons, detected beyond the scope of the disclosure. Such a reporting packet serve multiple purposes, including indicating whether interrupt masking has changed. If so, method 2300 may proceed to 2345. Otherwise, method 2300 may proceed to 2330 to determine if other reasons exist for generating a reporting packet.

At 2330, in one embodiment it may be determined whether a logical AND combination of the event tracing enable bit and necessary supporting trace parameters is transitioning from a zero to a one. This may represent, for example, that the last necessary condition to begin checking for interrupt masking changes has been met. If such a transition is detected, method 2300 may proceed to 2335. Otherwise, method 2300 may proceed to 2360.

At 2335, in one embodiment it may be determined whether the IF is presently different than was reported in a last reporting packet. If so, method 2300 may proceed to 2345. Otherwise, method 2300 may proceed to 2340. At 2340, in one embodiment it may be determined whether processor tracing was disabled since the last reporting packet was sent. Presently, as shown by element 2330, such processor tracing may be enabled. If processor tracing was disabled since the last reporting packet, method 2300 may proceed to 2345. Otherwise, method 2300 may proceed to 2360.

At 2345, in one embodiment the IF payload of the reporting packet may be set. In a further embodiment, the payload may be set to the current IF value. In another, further embodiment, the payload may be set to the current IF value in logical AND combination with the event tracing enabling.

At 2350, the reporting packet may be issued to processor tracing subscribers. At 2355, in one embodiment a FUP or TIP packet may be issued with the IP for which the new IF value applies.

At 2360, method 2300 may optionally repeat at, for example, 2305 or terminate. Method 2300 may optionally repeat in any suitable manner.

Embodiments of the mechanisms disclosed herein may be implemented in hardware, software, firmware, or a combination of such implementation approaches. Embodiments of the disclosure may be implemented as computer programs or program code executing on programmable systems comprising at least one processor, a storage system (including volatile and non-volatile memory and/or storage elements), at least one input device, and at least one output device.

Program code may be applied to input instructions to perform the functions described herein and generate output information. The output information may be applied to one or more output devices, in known fashion. For purposes of this application, a processing system may include any system that has a processor, such as, for example; a digital signal processor (DSP), a microcontroller, an application specific integrated circuit (ASIC), or a microprocessor.

The program code may be implemented in a high level procedural or object oriented programming language to communicate with a processing system. The program code may also be implemented in assembly or machine language, if desired. In fact, the mechanisms described herein are not limited in scope to any particular programming language. In any case, the language may be a compiled or interpreted language.

One or more aspects of at least one embodiment may be implemented by representative instructions stored on a machine-readable medium which represents various logic within the processor, which when read by a machine causes the machine to fabricate logic to perform the techniques described herein. Such representations, known as “IP cores” may be stored on a tangible, machine-readable medium and supplied to various customers or manufacturing facilities to load into the fabrication machines that actually make the logic or processor.

Such machine-readable storage media may include, without limitation, non-transitory, tangible arrangements of articles manufactured or formed by a machine or device, including storage media such as hard disks, any other type of disk including floppy disks, optical disks, Compact Disk Read-Only Memories (CD-ROMs), Compact Disk Rewritables (CD-RWs), and magneto-optical disks, semiconductor devices such as Read-Only Memories (ROMs), Random Access Memories (RAMs) such as Dynamic Random Access Memories (DRAMs), Static Random Access Memories (SRAMs), Erasable Programmable Read-Only Memories (EPROMs), flash memories, Electrically Erasable Programmable Read-Only Memories (EEPROMs), magnetic or optical cards, or any other type of media suitable for storing electronic instructions.

Accordingly, embodiments of the disclosure may also include non-transitory, tangible machine-readable media containing instructions or containing design data, such as Hardware Description Language (HDL), which defines structures, circuits, apparatuses, processors and/or system features described herein. Such embodiments may also be referred to as program products.

In some cases, an instruction converter may be used to convert an instruction from a source instruction set to a target instruction set. For example, the instruction converter may translate (e.g., using static binary translation, dynamic binary translation including dynamic compilation), morph, emulate, or otherwise convert an instruction to one or more other instructions to be processed by the core. The instruction converter may be implemented in software, hardware, firmware, or a combination thereof. The instruction converter may be on processor, off processor, or part-on and part-off processor. Thus, techniques for performing one or more instructions according to at least one embodiment are disclosed. While certain exemplary embodiments have been described and shown in the accompanying drawings, it is to be understood that such embodiments are merely illustrative of and not restrictive on other embodiments, and that such embodiments not be limited to the specific constructions and arrangements shown and described, since various other modifications may occur to those ordinarily skilled in the art upon studying this disclosure. In an area of technology such as this, where growth is fast and further advancements are not easily foreseen, the disclosed embodiments may be readily modifiable in arrangement and detail as facilitated by enabling technological advancements without departing from the principles of the present disclosure or the scope of the accompanying claims. the condition to include an interrupt, fault, or exception, has occurred on the processor during execution of the instructions

In some embodiments of the present disclosure, a processor may include a processor trace logical unit (PTLU). In combination with any of the above embodiments, in an embodiment the processor may include logic to produce branch execution records from execution of instructions, determine that a condition has occurred on the processor during execution of the instructions, determine whether event tracing is enabled for the processor, generate a CFE packet indicating a type of the condition, and to generate an indicator of an instruction address that generated the condition. In combination with any of the above embodiments, in an embodiment the processor may include logic to generate an EVD packet. In combination with any of the above embodiments, in an embodiment the EVD packet may specify supplemental information about the CFE packet. In combination with any of the above embodiments, in an embodiment the processor may include logic to transmit the EVD packet before the CFE packet. In combination with any of the above embodiments, in an embodiment the processor may include logic to generate a plurality of EVD packets. In combination with any of the above embodiments, in an embodiment the processor may include logic to transmit the EVD packets before the CFE packet. In combination with any of the above embodiments, in an embodiment the processor may include logic to determine an attempt to change an interrupt flag (IF), the change to indicate masking or unmasking of interrupts. In combination with any of the above embodiments, in an embodiment the processor may include logic to generate a reporting packet based upon the attempt to change the interrupt flag, the reporting packet to include a new value of the IF. In combination with any of the above embodiments, in an embodiment the processor may include logic to bind the reporting packet to an instruction pointer for which the change to the IF would apply. In combination with any of the above embodiments, in an embodiment the processor may include logic to generate a reporting packet based upon the attempt to change the interrupt flag and upon the determination of whether event tracing is enabled for the processor. In combination with any of the above embodiments, in an embodiment the processor may include logic to bind the reporting packet to an instruction pointer for which the change to the IF would apply by creating a follow-up or target message identifying the instruction pointer. In combination with any of the above embodiments, in an embodiment the processor may include determine whether tracking of interrupt flag (IF) masking has been enabled or disabled. In combination with any of the above embodiments, in an embodiment the processor may include logic to determine whether tracking of IF masking was enabled since a last reporting packet was sent. In combination with any of the above embodiments, in an embodiment the processor may include to generate a reporting packet, the packet to include the value of the IF, based upon enabling of interrupt flag masking and upon whether tracking of IF masking was enabled since the last reporting packet was sent. In combination with any of the above embodiments, in an embodiment the condition may be to include an interrupt, fault, or exception, has occurred on the processor during execution of the instructions. In combination with any of the above embodiments, in an embodiment the condition may be to require handling outside of the execution of instructions. In combination with any of the above embodiments, in an embodiment the condition may be to include an asynchronous event that has occurred on the processor. In combination with any of the above embodiments, in an embodiment the asynchronous event may include, for example, an interrupt, fault, exception, or a return from a software handler. In combination with any of the above embodiments, in an embodiment the condition may be to require handling of a message that is a return from an asynchronous event. In combination with any of the above embodiments, in an embodiment the return from the asynchronous even may include an interrupt return from an interrupt handler. In combination with any of the above embodiments, in an embodiment the return from the asynchronous event may include a fault return from a fault handler. In combination with any of the above embodiments, in an embodiment the return from the asynchronous even may include a VM event from a VM. In combination with any of the above embodiments, in an embodiment the condition may include events that are not or cannot be foreseen during execution of the instructions.

In some embodiments of the present disclosure, a system may include a system trace logical unit (PTLU). In combination with any of the above embodiments, in an embodiment the system may include logic to produce branch execution records from execution of instructions, determine that a condition has occurred on the system during execution of the instructions, determine whether event tracing is enabled for the system, generate a CFE packet indicating a type of the condition, and to generate an indicator of an instruction address that generated the condition. In combination with any of the above embodiments, in an embodiment the system may include logic to generate an EVD packet. In combination with any of the above embodiments, in an embodiment the EVD packet may specify supplemental information about the CFE packet. In combination with any of the above embodiments, in an embodiment the system may include logic to transmit the EVD packet before the CFE packet. In combination with any of the above embodiments, in an embodiment the system may include logic to generate a plurality of EVD packets. In combination with any of the above embodiments, in an embodiment the system may include logic to transmit the EVD packets before the CFE packet. In combination with any of the above embodiments, in an embodiment the system may include logic to determine an attempt to change an interrupt flag (IF), the change to indicate masking or unmasking of interrupts. In combination with any of the above embodiments, in an embodiment the system may include logic to generate a reporting packet based upon the attempt to change the interrupt flag, the reporting packet to include a new value of the IF. In combination with any of the above embodiments, in an embodiment the system may include logic to bind the reporting packet to an instruction pointer for which the change to the IF would apply. In combination with any of the above embodiments, in an embodiment the system may include logic to generate a reporting packet based upon the attempt to change the interrupt flag and upon the determination of whether event tracing is enabled for the system. In combination with any of the above embodiments, in an embodiment the system may include logic to bind the reporting packet to an instruction pointer for which the change to the IF would apply by creating a follow-up or target message identifying the instruction pointer. In combination with any of the above embodiments, in an embodiment the system may include determine whether tracking of interrupt flag (IF) masking has been enabled or disabled. In combination with any of the above embodiments, in an embodiment the system may include logic to determine whether tracking of IF masking was enabled since a last reporting packet was sent. In combination with any of the above embodiments, in an embodiment the system may include to generate a reporting packet, the packet to include the value of the IF, based upon enabling of interrupt flag masking and upon whether tracking of IF masking was enabled since the last reporting packet was sent. In combination with any of the above embodiments, in an embodiment the condition may be to include an interrupt, fault, or exception, has occurred on the system during execution of the instructions. In combination with any of the above embodiments, in an embodiment the condition may be to require handling outside of the execution of instructions. In combination with any of the above embodiments, in an embodiment the condition may be to include an asynchronous event that has occurred on the system. In combination with any of the above embodiments, in an embodiment the asynchronous event may include, for example, an interrupt, fault, exception, or a return from a software handler. In combination with any of the above embodiments, in an embodiment the condition may be to require handling of a message that is a return from an asynchronous event. In combination with any of the above embodiments, in an embodiment the return from the asynchronous even may include an interrupt return from an interrupt handler. In combination with any of the above embodiments, in an embodiment the return from the asynchronous event may include a fault return from a fault handler. In combination with any of the above embodiments, in an embodiment the return from the asynchronous even may include a VM event from a VM. In combination with any of the above embodiments, in an embodiment the condition may include events that are not or cannot be foreseen during execution of the instructions.

In some embodiments of the present disclosure, a PTLU may include logic to produce branch execution records from execution of instructions, determine that a condition has occurred on the PTLU during execution of the instructions, determine whether event tracing is enabled for a processor, generate a CFE packet indicating a type of the condition, and to generate an indicator of an instruction address that generated the condition. In combination with any of the above embodiments, in an embodiment the PTLU may include logic to generate an EVD packet. In combination with any of the above embodiments, in an embodiment the EVD packet may specify supplemental information about the CFE packet. In combination with any of the above embodiments, in an embodiment the PTLU may include logic to transmit the EVD packet before the CFE packet. In combination with any of the above embodiments, in an embodiment the PTLU may include logic to generate a plurality of EVD packets. In combination with any of the above embodiments, in an embodiment the PTLU may include logic to transmit the EVD packets before the CFE packet. In combination with any of the above embodiments, in an embodiment the PTLU may include logic to determine an attempt to change an interrupt flag (IF), the change to indicate masking or unmasking of interrupts. In combination with any of the above embodiments, in an embodiment the PTLU may include logic to generate a reporting packet based upon the attempt to change the interrupt flag, the reporting packet to include a new value of the IF. In combination with any of the above embodiments, in an embodiment the PTLU may include logic to bind the reporting packet to an instruction pointer for which the change to the IF would apply. In combination with any of the above embodiments, in an embodiment the PTLU may include logic to generate a reporting packet based upon the attempt to change the interrupt flag and upon the determination of whether event tracing is enabled for a processor. In combination with any of the above embodiments, in an embodiment the PTLU may include logic to bind the reporting packet to an instruction pointer for which the change to the IF would apply by creating a follow-up or target message identifying the instruction pointer. In combination with any of the above embodiments, in an embodiment the PTLU may include determine whether tracking of interrupt flag (IF) masking has been enabled or disabled. In combination with any of the above embodiments, in an embodiment the PTLU may include logic to determine whether tracking of IF masking was enabled since a last reporting packet was sent. In combination with any of the above embodiments, in an embodiment the PTLU may include to generate a reporting packet, the packet to include the value of the IF, based upon enabling of interrupt flag masking and upon whether tracking of IF masking was enabled since the last reporting packet was sent. In combination with any of the above embodiments, in an embodiment the condition may be to include an interrupt, fault, or exception, has occurred on the PTLU during execution of the instructions. In combination with any of the above embodiments, in an embodiment the condition may be to require handling outside of the execution of instructions. In combination with any of the above embodiments, in an embodiment the condition may be to include an asynchronous event that has occurred on the PTLU. In combination with any of the above embodiments, in an embodiment the asynchronous event may include, for example, an interrupt, fault, exception, or a return from a software handler. In combination with any of the above embodiments, in an embodiment the condition may be to require handling of a message that is a return from an asynchronous event. In combination with any of the above embodiments, in an embodiment the return from the asynchronous even may include an interrupt return from an interrupt handler. In combination with any of the above embodiments, in an embodiment the return from the asynchronous event may include a fault return from a fault handler. In combination with any of the above embodiments, in an embodiment the return from the asynchronous even may include a VM event from a VM. In combination with any of the above embodiments, in an embodiment the condition may include events that are not or cannot be foreseen during execution of the instructions.

In some embodiments, an apparatus may include means for tracing execution of instructions to produce branch execution records, determining that a condition has occurred on the processor during execution of the instructions, determining whether event tracing is enabled for the processor, generated in CFE to indicate a type of the condition, and generating an indicator of an instruction address that generated the condition. In combination with any of the above embodiments, in an embodiment the apparatus may include means for generating an EVD packet to specify supplemental information about the CFE packet. In combination with any of the above embodiments, in an embodiment the apparatus may include means for transmitting the EVD packet before the CFE packet. In combination with any of the above embodiments, in an embodiment the apparatus may include means for generating a plurality of EVD packets. In combination with any of the above embodiments, in an embodiment the apparatus may include means for transmitting the plurality of EVD packets before a corresponding CFE packet. In combination with any of the above embodiments, in an embodiment the apparatus may include means for determining an attempt to change an IF, the change to indicate masking or unmasking of interrupts. In combination with any of the above embodiments, in an embodiment the apparatus may include means for generating a reporting packet based upon the attempt to change the interrupt flag, the reporting packet to include a new value of the IF. In combination with any of the above embodiments, in an embodiment the apparatus may include means for binding the reporting packet to an instruction pointer for which the change to the IF would apply. In combination with any of the above embodiments, in an embodiment the apparatus may include means for generating a reporting packet based upon the attempt to change the interrupt flag and upon the determination of whether event tracing is enabled for the processor. In combination with any of the above embodiments, in an embodiment the apparatus may include means for binding the reporting packet to an instruction pointer for which the change to the IF would apply by creating a follow-up or target message identifying the instruction pointer. In combination with any of the above embodiments, in an embodiment the condition may be to include an interrupt, fault, or exception, has occurred on the PTLU during execution of the instructions. In combination with any of the above embodiments, in an embodiment the condition may be to require handling outside of the execution of instructions. In combination with any of the above embodiments, in an embodiment the condition may be to include an asynchronous event that has occurred on the PTLU. In combination with any of the above embodiments, in an embodiment the asynchronous event may include, for example, an interrupt, fault, exception, or a return from a software handler. In combination with any of the above embodiments, in an embodiment the condition may be to require handling of a message that is a return from an asynchronous event. In combination with any of the above embodiments, in an embodiment the return from the asynchronous even may include an interrupt return from an interrupt handler. In combination with any of the above embodiments, in an embodiment the return from the asynchronous event may include a fault return from a fault handler. In combination with any of the above embodiments, in an embodiment the return from the asynchronous even may include a VM event from a VM. In combination with any of the above embodiments, in an embodiment the condition may include events that are not or cannot be foreseen during execution of the instructions.

In some embodiments, an apparatus may include means for tracing execution of instructions to produce branch execution records, means for determining that a condition has occurred on the processor during execution of the instructions, means for determining whether event tracing is enabled for the processor, means for generating an CFE to indicate a type of the condition, and means for generating an indicator of an instruction address that generated the condition. In combination with any of the above embodiments, in an embodiment the apparatus may include means for generating an EVD packet to specify supplemental information about the CFE packet. In combination with any of the above embodiments, in an embodiment the apparatus may include means for transmitting the EVD packet before the CFE packet. In combination with any of the above embodiments, in an embodiment the apparatus may include means for generating a plurality of EVD packets. In combination with any of the above embodiments, in an embodiment the apparatus may include means for transmitting the plurality of EVD packets before a corresponding CFE packet. In combination with any of the above embodiments, in an embodiment the apparatus may include means for determining an attempt to change an IF. In combination with any of the above embodiments, in an embodiment the change may indicate masking or unmasking of interrupts. In combination with any of the above embodiments, in an embodiment the apparatus may include means for generating a reporting packet based upon the attempt to change the interrupt flag, the reporting packet to include a new value of the IF. In combination with any of the above embodiments, in an embodiment the apparatus may include means for binding the reporting packet to an instruction pointer for which the change to the IF would apply. In combination with any of the above embodiments, in an embodiment the apparatus may include means for generating a reporting packet based upon the attempt to change the interrupt flag and upon the determination of whether event tracing is enabled for the processor. In combination with any of the above embodiments, in an embodiment the apparatus may include means for binding the reporting packet to an instruction pointer for which the change to the IF would apply by creating a follow-up or target message identifying the instruction pointer. In combination with any of the above embodiments, in an embodiment the condition may be to include an interrupt, fault, or exception, has occurred on the PTLU during execution of the instructions. In combination with any of the above embodiments, in an embodiment the condition may be to require handling outside of the execution of instructions. In combination with any of the above embodiments, in an embodiment the condition may be to include an asynchronous event that has occurred on the PTLU. In combination with any of the above embodiments, in an embodiment the asynchronous event may include, for example, an interrupt, fault, exception, or a return from a software handler. In combination with any of the above embodiments, in an embodiment the condition may be to require handling of a message that is a return from an asynchronous event. In combination with any of the above embodiments, in an embodiment the return from the asynchronous even may include an interrupt return from an interrupt handler. In combination with any of the above embodiments, in an embodiment the return from the asynchronous event may include a fault return from a fault handler. In combination with any of the above embodiments, in an embodiment the return from the asynchronous even may include a VM event from a VM. In combination with any of the above embodiments, in an embodiment the condition may include events that are not or cannot be foreseen during execution of the instructions. 

What is claimed is:
 1. A processor, comprising: a processor trace logical unit (PTLU), including a first logic to produce branch execution records from execution of instructions; a second logic to determine that a condition, the condition to include an asynchronous event or a return from a software handler for an asynchronous event, has occurred on the processor during execution of the instructions; a third logic to determine whether event tracing is enabled for the processor; a fourth logic to generate a control flow event (CFE) packet, the CFE packet to indicate a type of the condition; and a fifth logic to generate an indicator of an instruction address that generated the condition.
 2. The processor of claim 1, further comprising a sixth logic to generate an event data (EVD) packet, the EVD packet to specify supplemental information about the CFE packet.
 3. The processor of claim 1, further comprising: a sixth logic to generate an event data (EVD) packet, the EVD packet to specify supplemental information about the CFE packet; and a seventh logic to transmit the EVD packet before the CFE packet.
 4. The processor of claim 1, further comprising: a sixth logic to generate a plurality of event data (EVD) packets, the EVD packets to specify supplemental information about the CFE packet; and a seventh logic to transmit the EVD packets before the CFE packet.
 5. The processor of claim 1, further comprising: a sixth logic to determine an attempt to change an interrupt flag (IF), the change to indicate masking or unmasking of interrupts; a seventh logic to generate a reporting packet based upon the attempt to change the interrupt flag, the reporting packet to include a new value of the IF; and an eighth logic to bind the reporting packet to an instruction pointer for which the change to the IF would apply.
 6. The processor of claim 1, further comprising: a sixth logic to determine an attempt to change an interrupt flag (IF), the change to indicate masking of interrupts; a seventh logic to generate a reporting packet based upon the attempt to change the interrupt flag and upon the determination of whether event tracing is enabled for the processor; and an eighth logic to bind the reporting packet to an instruction pointer for which the change to the IF would apply by creating a follow-up or target message identifying the instruction pointer.
 7. The processor of claim 1, further comprising: a sixth logic to determine whether tracking of interrupt flag (IF) masking has been enabled or disabled; a seventh logic to determine whether tracking of IF masking was enabled since a last reporting packet was sent; and an eighth logic to generate a reporting packet, the packet to include the value of the IF, based upon enabling of interrupt flag masking and upon whether tracking of IF masking was enabled since the last reporting packet was sent.
 8. A method comprising, within a processor: tracing execution of instructions to produce branch execution records; determining that a condition, the condition to include an asynchronous event or a return from a software handler for an asynchronous event, has occurred on the processor during execution of the instructions; determining whether event tracing is enabled for the processor; generating a control flow event (CFE) packet, the CFE packet to indicate a type of the condition; and generating an indicator of an instruction address that generated the condition.
 9. The method of claim 8, further comprising generating an event data (EVD) packet, the EVD packet to specify supplemental information about the CFE packet.
 10. The method of claim 8, further comprising: generating an event data (EVD) packet, the EVD packet to specify supplemental information about the CFE packet; and transmitting the EVD packet before the CFE packet.
 11. The method of claim 8, further comprising: generating a plurality of event data (EVD) packets, the EVD packets to specify supplemental information about the CFE packet; and transmitting the EVD packets before the CFE packet.
 12. The method of claim 8, further comprising: determining an attempt to change an interrupt flag (IF), the change to indicate masking or unmasking of interrupts; generating a reporting packet based upon the attempt to change the interrupt flag, the reporting packet to include a new value of the IF; and binding the reporting packet to an instruction pointer for which the change to the IF would apply.
 13. The method of claim 8, further comprising: determining an attempt to change an interrupt flag (IF), the change to indicate masking of interrupts; generating a reporting packet based upon the attempt to change the interrupt flag and upon the determination of whether event tracing is enabled for the processor; and binding the reporting packet to an instruction pointer for which the change to the IF would apply by creating a follow-up or target message identifying the instruction pointer.
 14. A system, comprising: a processor trace logical unit (PTLU), including a first logic to produce branch execution records from execution of instructions; a second logic to determine that a condition, the condition to include an asynchronous event or a return from a software handler for an asynchronous event, has occurred on the system during execution of the instructions; a third logic to determine whether event tracing is enabled for the system; a fourth logic to generate a control flow event (CFE) packet, the CFE packet to indicate a type of the condition; and a fifth logic to generate an indicator of an instruction address that generated the condition.
 15. The system of claim 14, further comprising a sixth logic to generate an event data (EVD) packet, the EVD packet to specify supplemental information about the CFE packet.
 16. The system of claim 14, further comprising: a sixth logic to generate an event data (EVD) packet, the EVD packet to specify supplemental information about the CFE packet; and a seventh logic to transmit the EVD packet before the CFE packet.
 17. The system of claim 14, further comprising: a sixth logic to generate a plurality of event data (EVD) packets, the EVD packets to specify supplemental information about the CFE packet; and a seventh logic to transmit the EVD packets before the CFE packet.
 18. The system of claim 14, further comprising: a sixth logic to determine an attempt to change an interrupt flag (IF), the change to indicate masking or unmasking of interrupts; a seventh logic to generate a reporting packet based upon the attempt to change the interrupt flag, the reporting packet to include a new value of the IF; and an eighth logic to bind the reporting packet to an instruction pointer for which the change to the IF would apply.
 19. The system of claim 14, further comprising: a sixth logic to determine an attempt to change an interrupt flag (IF), the change to indicate masking of interrupts; a seventh logic to generate a reporting packet based upon the attempt to change the interrupt flag and upon the determination of whether event tracing is enabled for the system; and an eighth logic to bind the reporting packet to an instruction pointer for which the change to the IF would apply by creating a follow-up or target message identifying the instruction pointer.
 20. The system of claim 14, further comprising: a sixth logic to determine whether tracking of interrupt flag (IF) masking has been enabled; a seventh logic to determine whether tracking of IF masking was enabled since a last reporting packet was sent; and an eighth logic to generate a reporting packet, the packet to include the value of the IF, based upon enabling the interrupt flag masking and upon whether tracking of IF masking was enabled since the last reporting packet was sent. 